This is normal behaviour when saving a structured FrameMaker book to XML. What's happening is that the entire book becomes a single XML instance, but one that is built from a series of 'entities'. The XML file that is produced will include an entity definition and matching entity reference for each of those files with the strange extension. One entity per book component. Despite the apparently odd output, if the source book was valid, then the XML output should be valid too.
The unusual extension is used to avoid file name collisions. No two files could ever have the same name using this method, also it's best not to name them .xml because the unstructured generated files will never be well formed XML.
One way to get the XML into a single file, rather than the separate entity files is to apply an XSLT transformation on the output. XSLT always resolves entities, so the end result is one much larger XML file. The XSLT only has to provide the most basic identity transform to work its magic.
Here's a small example of the results:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE book SYSTEM "file:///C:/Test/Application/TestFM.dtd" [
<!-- Begin Document Specific Declarations -->
<!ENTITY bkc1 SYSTEM "preface1.e01">
<!ENTITY bkc2 SYSTEM "Chapter1.e02">
<!-- End Document Specific Declarations -->
]>
<book xml:lang = "en"
xmlns:xlink = "http://www.w3.org/1999/xlink">&bkc1;&bkc2;</book>
On lines 06 and 07 we see definitions for the entities bkc1 and bkc2 which map to the XML fragments preface1.e0 and Chapter.e02 repectively. Then on line 13 we see the entity references which tell us where the entities should be placed in the complete XML instance.
Let me know if you need any more guidance on any of this.
Ian
p.S. This thread will probably be moved to the Structured FrameMaker forum by the moderators.
AdChoices