FWIW, I vote for separate chapter files too. I prefer the generated TOC and
Index book files, instead of generating standalone files and pasting them in
- Original Message -
From: "Lin Sims"
To: "Ken Poshedly" ,
I thought you were talking about separate .fm files for ease of
generating separate PDFs.
Otherwise, individual .fm files for each chapter seem to me like a
relic of the days when computers didn't have enough memory to handle a
If you have to embed the graphics, that might be a
I agree with Rick Quatro.
From: Framers [mailto:email@example.com]
On Behalf Of Robert Lauriston
Sent: Monday, November 07, 2016 1:06 PM
Subject: [EXTERNAL] Re: [Framers] Pros/Cons: Separate file
Pretty much what it says in the title. I'm guessing there have been
discussions about this in the past, and I plan to look for those, but I
thought I'd toss this out there anyway.
We're talking chapters that can run a couple hundred (or more) pages loaded
with tables, graphics, and conditional
No question in my mind: Separate files for each chapter, mainly because it
easier to author, reorganize, and maintain separate FrameMaker documents.
FrameMaker books work quite well for organizing documents. Please let me
know if you have any questions or comments.
We also use unstructured FM11.0 to produce files that are distilled down to pdf
files for hard copy printing (and maybe distribution on CD, but not so much).
As such, we compile separate chapter files then assemble them into a final book
Much more manageable that way (at least for
Also beneficial for multiple editors working on the same book in different
chapters and configuration control when one chapter is changed often and
others rarely change. I also have other elements such as large tables that
are maintained externally or commonly used content managed as external
Going public on this...
I think the question is, what would be the advantages of putting multiple
chapters in a single document? FrameMaker has supported the 'book' concept
almost from the get-go: why on earth would you not want to use it?
(I am ever-open to suggestions ;-)
Here is another vote for a separate file per chapter. Also make your
images references and resize them (120ppi and less than your page width
is a good rule of thumb).
Happy user of Frame since 1990.
On November 7, 2016 at 11:54 AM Rick Quatro
I think I touched a nerve.
Yeah, my personal inclination is one chapter per file, unless we're talking
a really short document of less than 20 pages. Nice to know that I'm not
alone; however, I'm really looking for reasons why using a chapter per file
is better than using one file for an entire
I always do one file, unless it gets so big that there are download
problems. Then everything can be cross-referenced. You can have
cross-PDF links, but they're more problematic. As a user, I always
find it frustrating when large documents are split up.
How big is the file if you generate one big
The issue is not a single PDF versus separate PDFs for each chapter. The
issue is separate FrameMaker files for each chapter. With separate chapters
managed in a FrameMaker book, you still create a single PDF for your output.
The book PDFs usually run in the 3-10MB range. Individual chapters in FM
format can run up to 30MB or more. And as Rick said, we're talking about a
single FM file per chapter in a book, then generating a single PDF for the
book, not separate PDFs for each chapter.
(I wish we could reference
Mail list logo