Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

XML Graphic File Handling

Explorer ,
May 04, 2010 May 04, 2010

I have a CDATA (string) attribute on a tag that is the filename for a referenced graphic:

<graphicobject entity="P32-01-1.tif">

This displays the graphic fine but I always get an error:

C:\Users\jmonaco\AppData\Local\Temp\FMT2A6D.tmp; line 1095

Bad entity name (P32-01-1.tif) was specified for an imported graphic.

RW File:

element "graphicobject" {
       is fm graphic element "graphicobject";
       attribute "entity" is fm property entity;
       attribute "file" drop;
       attribute "dpi" drop;
       attribute "impby" drop;
       fm property import by reference or copy value is "Ref" ;
}

Does the name "entity" imply some real entity processing?

If the name of the attribute were different would Frame still process the graphic correctly using just he path to the graphic?

I do not want any entity processing if possible.

Thanks - Jim

XML Read Messages (Document Instance)

TOPICS
Structured
914
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Guide , May 04, 2010 May 04, 2010

Jim,

I do not know much about entities and the attribute entity, but your read/write rule needs to associate the graphic's file name with the frame property file. Thus, the rule would be:

attribute "filename" is fm property file;

The above assumes you have changed YOUR attribute entity to filename. If you keep the attribute name entity, then the rule would be:

attribute "entity" is fm property file;

HOWEVER, I am not sure this is wise because there is both a frame property entity and a frame property

...
Translate
Guide ,
May 04, 2010 May 04, 2010

Jim,

I do not know much about entities and the attribute entity, but your read/write rule needs to associate the graphic's file name with the frame property file. Thus, the rule would be:

attribute "filename" is fm property file;

The above assumes you have changed YOUR attribute entity to filename. If you keep the attribute name entity, then the rule would be:

attribute "entity" is fm property file;

HOWEVER, I am not sure this is wise because there is both a frame property entity and a frame property file.

Van

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 04, 2010 May 04, 2010

Perfect - worked like a charm...

Thanks - Jim

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Advisor ,
May 15, 2010 May 15, 2010

Jim,

  Glad your application is working. Here are some more details for future reference.

  A graphic element can have a file attribute, an entity attribute, or both. The value of a file atttribute is the name of the graphic file. The value of an entity attribute is the name of an unparsed entity that is declared in the internal or external DTD subset. For example, suppose adocument starts something like:

<!DOCTYPE xxx SYSTEM "mydtd.dtd" [

    <!ENTITY Lassie SYSTEM "dog.jpg" NDATA jpeg>

]>

  The same graphic can be identified by setting a file attribute to "dog.jpg" or an entity attribute to "Lassie".

  If a graphic element has both a file attribute and an entity attribute, FrameMaker uses the entity attribute when it writes XML.

  A read/write rule to identify an attribute as a file or entity attribute is only needed if the attribute name is not "file" in the case of a file attribute and not "entity" in the case of an entity attribute.

     --Lynne

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
May 15, 2010 May 15, 2010
LATEST

Thanks Lynne - your last paragraph was the most helpful.  I had an attribute called entity in the data that in the original SGML was an entity.   Whne we converted to XML we wanted it to be a file attribute but did not want to change the name in all of the data files.  Fixing up the RW rules made it do what I wanted.

Thanks - Jim

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines