Adobe 65030365 Developer's Guide - Page 369

24 Modifications to the default translation Each text entity starts with the appropriate document processing instruction. Thus, the entity bkc2 has the form: . . . When FrameMaker exports a book, it creates a new file for each structured document. Unstructured documents appear as text within an element. In general, you can use a different EDD for each document in a FrameMaker book. However, if you export the book to markup, the result will be invalid unless the DTD provides a superset of the element declarations used in all the EDDs. Modifications to the default translation FrameMaker provides a small number of read/write rules specific to translating books. In addition, there are rules relevant to translating files within books. If you need to make other changes to the translation, you write a structure API client. To specify the handling of unstructured documents, you specify the handling of the containing element. • To discard a document, use the drop rule described in "drop" on page 373. • To import or export a document as an empty element, use the drop content rule described in "drop content" on page 375. For a summary of read/write rules relevant to translating books and book components, see "Books" on page 356. Using elements to identify book components on import The default method to specify how a markup document should be broken into components of a FrameMaker book is with the processing instructions described above. However, you may be able to use rules for this purpose instead. If you can identify elements in your DTD that correspond to where you want file breaks in FrameMaker, you can use this rule: reader generate book put element "gi" in file ["fname"]; For example, if you want instances of the chapter and section elements to indicate new files, you can use these rules: reader generate book { put element "section" in file "Sect.fm"; put element "chapter" in file; } Structure Application Developer's Guide 351