It does that automatically now, although it's still faster if you have them
all open. I usually have all my files open anyway for xref creation so it's
never been an issue for me.
On Fri, Jan 10, 2020 at 12:44 PM Robert Lauriston
wrote:
> Oh, there's a blast from the past. In FM7 there was some
Oh, there's a blast from the past. In FM7 there was some issue that
meant I had to open all the files in a book when saving as PDF. That
was one of the incentives for putting all the chapters in a single .fm
file.
On Thu, Jan 9, 2020 at 8:06 AM Lin Sims wrote:
>
> Holding down Shift, not Ctrl.
SuuUUre.
That's your story, and you're sticking to it, huh?
(Right there with you, actually.)
On Thu, Jan 9, 2020 at 2:51 PM Fred Ridder wrote:
> Oops, right. I knew it was one of those keys in the lower left corner. My
> fingers know better then my mind sometimes...
>
> -FR
>
>
Oops, right. I knew it was one of those keys in the lower left corner. My
fingers know better then my mind sometimes...
-FR
From: Framers on
behalf of Lin Sims
Sent: Thursday, January 9, 2020 11:06 AM
To: An email list for people using Adobe FrameMaker
I've never used a comment marker. I didn't even know they existed, but
that's mostly because I don't use markers much. I should probably look into
their functionality.
For me, I just create a condition tag for comments because that makes it
easy to find and edit comments.
On Thu, Jan 9, 2020 at
At 03:17 AM 1/9/2020, barry.meis...@nuvoton.com wrote:
I have a particularly long book (about 30 files, 1200 pages total,
non-structured FM) that "dies" in the middle (towards the first
third, actually) of the update (book generation).
Hi Barry,
You didn't say specifically what happens when
Holding down Shift, not Ctrl. :D
On Thu, Jan 9, 2020 at 10:21 AM Fred Ridder wrote:
> Have you tried opening all the component files before you kick off the
> update book operation? If you don't do this, any kind of "informational"
> dialog like the infamous "missing fonts" message or
Have you tried opening all the component files before you kick off the update
book operation? If you don't do this, any kind of "informational" dialog like
the infamous "missing fonts" message or "inconsistent conditions" or
"inconsistent color definitions" messages will make the book update
My go-to is performing a MIF wash of the book. Adobe actually has a DLL for
that which, for some reason, it doesn't include as part of the basic
installation (see
https://helpx.adobe.com/framemaker/kb/how-to-use-mifwash-utility-in-framemaker.html)
.
If that doesn't work, I start working my way
Hi,
I have a particularly long book (about 30 files, 1200 pages total,
non-structured FM) that "dies" in the middle (towards the first third,
actually) of the update (book generation).
I update other books successfully---all the time. It's just this one book that
has been causing me
10 matches
Mail list logo
