Ah - solved my own problem with help of 'Publishing Fundamentals: Unstructured
Framemaker'.
Set the numbering to continue from previous page in book. I don't know why this
wasn't set in my original template.
From: framers-boun...@lists.frameusers.com
Ignore previous email.
I have documents that start with a tag called 'ChapTitle' and some that start
with Heading1.
The reference pages are set up so that pages with 'ChapTitle' on them will use
the 'First' master page. This has a header with the chapter number in it. Pages
starting with
Hi Ken,
I have used FM11 unstructured on Win7 with files on the network since FM11
was released. I have no problems.
Maybe your files are too big with the embedded ages?
On Thursday, August 8, 2013, Ken Poshedly wrote:
Due to the addition of 2 new contract writers and the replacement of the
I have used FM 11 with Windows 7 working on files from a network for months
and, while not crash free, I have experienced relatively few crashes. The
first patch that adobe released help a lot with printing issues.
Craig
From: framers-boun...@lists.frameusers.com
It's been a big project, but we were successful!
Here's the skinny:
I need to import unstructured FM content into a new SalesForce Knowledge
knowledge base. Individual procedures written in FM11 get published out via
Mif2Go as Standard HTML (not help), and then imported by SalesForce with
the help
I recently upgraded from Frame 7.2 to 11 and have found that some of my
reference page elements didn't make the transition very well.
I have 2-column, 1-row tables with Note, Important, or Warning in the
first cell. These labels are non-anchored frames in the reference page and
appeared just
Hi Ken,
One option that you have is to put your files in a SVN repository. If you
do this, then checked out files will be local to the person's computer and
there's no issue with network latency etc. You can certainly do the check
out to an external hard drive to if that's needed. Once the user
You are one tremendously lucky person to avoid a crash for that long. FM
crashes on me a couple of times a week on average. How much RAM do you have
on your system?
On the SUN workstations we never saw a crash. But that was FMv5.5.
Craig
Win7, 8GB
From:
What you describe is true because the continue from previous file in book
numbering option is not a property of a chapter file. Because that option only
has relevance when the file is part of a book, the behavior can only be set as
part of the book file's properties. This logic allows the same
I've been running the combo for a couple years on multiple systems and
crashes are really few and far between,..
Very stable, IMHO.
ONE OTHER factor -- if you have aggressive anti-virus software
enabled, that's one other point of potential failure. Why? If your
book or document includes multiple
First, if you updated the file by opening the 7 as an 11 and saving,
I'd save the file as a .mif and open that to ensure that you're
working in a file without extra characters and any possible 7 hangover
effects.
Once you know you have clean files, the first things I'd check would
be your table
At 01:32 a.m. 10/08/2013, Rick Quatro wrote:
>
>Otherwise, make sure the writers have plenty of RAM. In my opinion, 8 GB is
>the minimum. This may help with the performance problems.
>
More than 4 GB of RAM is of absolutely no use for running a 32-bit application,
whether it be on a 32-bit or
rameusers.com/pipermail/framers/attachments/20130810/d72abc72/attachment.html>
I've been running the combo for a couple years on multiple systems and
crashes are really few and far between,..
Very stable, IMHO.
ONE OTHER factor -- if you have aggressive anti-virus software
enabled, that's one other point of potential failure. Why? If your
book or document includes multiple
First, if you updated the file by opening the 7 as an 11 and saving,
I'd save the file as a .mif and open that to ensure that you're
working in a file without extra characters and any possible 7 hangover
effects.
Once you know you have clean files, the first things I'd check would
be your table
15 matches
Mail list logo
