Article View: adobe.framemaker.sgml
Article #110Re: Keeping graphic paths during conversion from FM to xml
From: Michael_Mueller-Hillebrand
Date: Tue, 10 Feb 2009 10:48
Date: Tue, 10 Feb 2009 10:48
14 lines
1322 bytes
1322 bytes
Anna,
are you sure the "new graphics" are shown because of the new attribute? The path to external graphics is a FrameMaker property (not an attribute) which is never visible inside the FrameMaker document structure (like e.g. the number of table columns).
I guess (or suggest) that note graphics like the one you are using, are included in the documents by means of the Frame Above/Below feature and included only on a Reference Page. Maybe that is what the template designer did (or should do).
Anyway, to export the path of a referenced graphic you would use a read/write rule similar to
element "image" {
is fm graphic element;
attribute "href" is fm property file;
}
- Michael
Technical Details
Message-ID:
<59b7d333.0@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!newshub.sdsu.edu!webcrossingReferences:
<59b7d333.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: fcc08,be3032cdebd517d1 X-Google-Attributes: gidfcc08,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: Michael_Mueller-Hillebrand@adobeforums.com Path: arc1-ca.pugleaf.net!g2news1.google.com!news1.google.com!newshub.sdsu.edu!webcrossing Newsgroups: adobe.framemaker.sgml Subject: Re: Keeping graphic paths during conversion from FM to xml Message-ID: <59b7d333.0@webcrossing.la2eafNXanI> Date: Tue, 10 Feb 2009 02:48:47 -0800 References: <59b7d333.-1@webcrossing.la2eafNXanI> Lines: 21 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit