can ENTITY ImportedGraphic - be omitted?

[Wim Hooghwinkel (Scriptware)]

Hello Lynn,

thanks you for your quick response. Your suggestion to use 'the function
unparsed-entity-uri' works, thanks!

I can not get the corrcet syntax for FM to export only as file, not as
entity. It keeps on exporting it as an entity, even when I delete the
entity reference page and use the 'attribute "entity" is fm attribute'
rule (FM won't import graphics that are declared by entitys though).


Met vriendelijke groet / kind regards,

Wim Hooghwinkel wimh at scriptware.nl
DTP and XML Management

Scriptware bv http://www.scriptware.nl
tel : +31 (0)23 548 48 84
fax : +31 (0)23 548 48 85
http://www.scriptware.nl
info at scriptware.nl info at scriptware.nl 

-----Original Message-----
From: Lynne A. Price [mailto:lprice at txstruct.com] 
Sent: Thursday, August 17, 2006 3:31 PM
To: Wim Hooghwinkel (Scriptware); Frame 
Subject: Re: can ENTITY ImportedGraphic - be omitted?

At 05:45 AM 8/17/2006, Wim Hooghwinkel \(Scriptware\) wrote:
>when FM saves an XML file, it writes the graphics as entitys in the 
>header of the XML.
>
>Can this be changed - to keep the graphic references in the XML body?
>
>Problem is, that we want to use some XSLT to preprocess or postprocess 
>the XML files and it seems to be impossible to keep the header with the

>entity references. Has anyone yet a work around for this?  (FM 7.2).

Wim,

1) FM can export a graphic using either an ENTITY attribute (default
name is entity) or a CDATA attribute (default name is file). The value
of the former is the name of an unparsed entity whose system identifier
names the graphic file; the value of the latter is the name of the
graphic file. If the DTD declares both attributes, FM uses the ENTITY
attribute.

You can specify the attribute names with read/write rules such as:

     element "image" {
        is fm graphic element;
        attribute "graphicfile" is fm property file;
        attribute "graphicentity" is fm property entity;
        }

These rules allow FM to import files that use either graphicfile or
graphicentity, but on export it would always use graphicentity.  If you
want it to export only graphicfile, remove the rule for graphicentity.
If you want to export using graphicfile, but to be able to import either
form, you'll need to use different rules for opening XML documents and
saving documents as XML.

If your DTD happens to declare an ENTITY attribute named entity and you
don't want FM to use it for exporting graphics, use the rule:

     attribute "entity" is fm attribute;

2) While XSLT cannot simply copy the internal DTD subset of the document
it is processing, it can generate a new one with entity declarations
equivalent to those in the original. Use the function
unparsed-entity-uri to write such a transform.

         --Lynne


Lynne A. Price
Text Structure Consulting, Inc.
Specializing in structured FrameMaker consulting, application
development, and training
lprice at txstruct.com            http://www.txstruct.com
voice/fax: (510) 583-1505      cell phone: (510) 421-2284