--Original Message-
From: Framers
[mailto:framers-bounces+tammyvb=spectrumwritingllc@lists.frameusers.com]
On Behalf Of Robert Lauriston
Sent: Tuesday, November 08, 2016 1:05 PM
To: framers@lists.frameusers.com
Subject: Re: [Framers] Pros/Cons: Separate file per chapter, or one REALLY
BIG F
That's a good point. For multiple writers to work on the same
document, it needs to be split into multiple files.
Though in that case you might better migrate from FrameMaker to
something that was designed for collaboration.
On Tue, Nov 8, 2016 at 10:00 AM, Craig, Alison wrote:
>... you can shar
meusers.com] On Behalf
Of Rick Quatro
Sent: Monday, November 07, 2016 10:55 AM
To: 'Lin Sims'; 'Frame Users'
Subject: Re: [Framers] Pros/Cons: Separate file per chapter, or one REALLY BIG
FILE for an entire book
Hi Lin,
No question in my mind: Separate files for each chapter,
PS:
The only time FrameMaker did not work well was when I imported a multiterm
database export file (as xml via structured application).
I had to split up the original xml into 3 parts, and although this was only
text, it took FrameMaker more than one hour to open one of the parts (as the
resu
Hi Lin,
we are producing multi-lingual FM books out of an XML-CMS, so we do not
have to handle the FM files for editorial purposes.
I prefer the single file (per language), because we often had problems
with the left/right pagination rules and special left/right masterpages
for the start of the
;
, "Rick Quatro"
Cc: "Frame Users"
Sent: Monday, November 7, 2016 1:13:31 PM
Subject: Re: [Framers] Pros/Cons: Separate file per chapter, or one REALLY BIG
FILE for an entire book
I think I touched a nerve.
Yeah, my personal inclination is one chapter per file, unless we&
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
whole book.
If you have to embed the graphics, that might be a specia
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 images
=rickquatro@lists.frameusers.com] On Behalf
Of Robert Lauriston
Sent: Monday, November 07, 2016 2:44 PM
To: framers@lists.frameusers.com
Subject: Re: [Framers] Pros/Cons: Separate file per chapter, or one REALLY
BIG FILE for an entire book
I always do one file, unless it gets so big that there
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).
Grant
Happy user of Frame since 1990.
On November 7, 2016 at 11:54 AM Rick Quatro
wrote:
Hi Lin,
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
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 ;-)
--
Steve
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
entit
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 b
Lin,
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
in FM.
Much more manageable that way (at least for us
Hi Lin,
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.
Rick
Rick Quatro
Carme
16 matches
Mail list logo
