Skip to main content
_
_Anna_Furtner_
Participant
February 9, 2009
Question

Keeping graphic paths during conversion from FM to xml

  • February 9, 2009
  • 2 replies
  • 537 views
Hi All,

I'm converting unstructured FM-documents to structured FM-documents and then to xml.
In my conversion table I put in graphics instead of certain paragraph formats:
P:pi_hinw -> image[href="../bilder/piktogramme/hinweis_de.eps"]

So far everything works fine.
In my structured FM-Dokuments the new graphics are displayed as well as the old ones which already were in the unstructered FM-Document.

Now if I convert the structured FM-document to an xml-document, the graphic paths of my old graphics are lost. But the new ones (image[href="../bilder/piktogramme/hinweis_de.eps"]) are still displayed.

If I save the stuctured FM-document as xml-document, FM somehow does convert the graph paths of the old graphics, but the new ones are lost!

Is there a way, I can keep both during conversion to xml:
old graphic paths which are hidden somewhere in FM and new ones which are stored in an attribute?

Thanks in advance,
Anna
This topic has been closed for replies.

2 replies

_
_Anna_Furtner_Author
Participant
February 10, 2009
Hi Michael,

I'm quite sure that the "new graphics" are shown because of the new attributes. At least the attributes are displayed in FM (I had a look in the Structure View and also opened the Attribute window).
It is already the structured FM-document, I'm writing about here.
So I don't unterstand why the path to the external graphic could not be inserted in an attribute.
Also, what I don't understand is: Why does FM delete the existing attributes when I save my FM-document directly as xml?

I tried to convert the structured FM-document with a separate application just for converting. In the read/write rules for this application I have tried exactly the rule you suggested (and also a few alternatives).
If I choose "StructureTools > Utlities > Convert Docmunets to Structured Format" to convert the FM-document, the "old graphics" with the hidden path vanish and only the "new graphics" stay in the document.
-> The read/write rule does not help much here.
But I assumed as much as I was browsing the other topics in this forum.

I guess the only way to keep the graphics with the hidden path is to save the FM-document as xml.
So I have the choice between keeping my cross-refs and the note grpahics or keeping the old graphics. Am I right?

By the way: You are right. In our unstructured documents the note graphics are included by a Reference Page. But the not graphics contain text and as we want to keep our templated non-verbal, we decided to not insert the note graphics by a Reference Page anymore.

Anna
M
Michael_Müller-Hillebrand-basb
Inspiring
February 10, 2009
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
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices