Article View: adobe.framemaker
Article #2094Re: Why bother using the book construct?
From: Dave_Hayes
Date: Thu, 09 Oct 2008 11:03
Date: Thu, 09 Oct 2008 11:03
6 lines
1423 bytes
1423 bytes
Don, just to clarify things, I think the way you are using the terms Chapter, Book, and Document is at odds with the way these terms are used in the FM manual. For example, referring to the files in a book as "books" or "book files" is confusing. In the context of FrameMaker, here's how I use these terms: A manual (which you can hold in your hand) is a book. A FrameMaker book file is a file with a .book filename extension, and it represents one entire book (one entire manual). A FrameMaker book file contains a list of the FrameMaker document files that make up the book. A FrameMaker document file has a .fm filename extension, and it can be a single chapter, an appendix, or a generated file such as a table of contents. You can use the same document file (chapter file) in more than one book if you want.
Technical Details
Message-ID:
<59b68482.8@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!newshub.sdsu.edu!feeder.erje.net!news4us.nl!webcrossingReferences:
<59b68482.-1@webcrossing.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Thread: fd315,43691471f647136c X-Google-Attributes: gidfd315,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit From: Dave_Hayes@adobeforums.com Newsgroups: adobe.framemaker Subject: Re: Why bother using the book construct? Message-ID: <59b68482.8@webcrossing.la2eafNXanI> Date: Thu, 9 Oct 2008 04:03:28 -0700 References: <59b68482.-1@webcrossing.la2eafNXanI> Lines: 15 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news1.google.com!newshub.sdsu.edu!feeder.erje.net!news4us.nl!webcrossing