If I did every topic separately and added more for chunks smaller than a
topic, I'd be around 1000.
I'm the lone writer so I don't work on the network. My current work is
always local (regular backups made to other locations of course!) so
that's not part of the speed problem. All I know is
Judy, so how many insets is that? Tens, or hundreds, or thousands?
To me, 50% utilization isn't much and I wouldn't be concerned... but
when you start juggling hundreds of files, there's a corresponding hit
on the operating system and network traffic; it's larger than just in
FM. Within FM, you ca
Art and Richard both recommended the idea of insetting topic body text
between the headings in a container doc. My biggest qualm about using
container docs with all of the headings then insetting the body text is
the sheer number of insets.
I recently tried breaking my doc set into topic-size
If I did every topic separately and added more for chunks smaller than a
topic, I'd be around 1000.
I'm the lone writer so I don't work on the network. My current work is
always local (regular backups made to other locations of course!) so
that's not part of the speed problem. All I know is
Judy wrote:
> I recently tried breaking my doc set into topic-sized fm docs, then
> building the different outputs with the topic fm's as insets to a
> chapter container. It worked great w/ 1 chapter, but when I tested it
> with the first 3 chapters, FM couldn't handle it. (50% CPU usage on
a
Judy wrote:
> I recently tried breaking my doc set into topic-sized fm docs, then
> building the different outputs with the topic fm's as insets to a
> chapter container. It worked great w/ 1 chapter, but when I tested it
> with the first 3 chapters, FM couldn't handle it. (50% CPU usage on
a
Judy, so how many insets is that? Tens, or hundreds, or thousands?
To me, 50% utilization isn't much and I wouldn't be concerned... but
when you start juggling hundreds of files, there's a corresponding hit
on the operating system and network traffic; it's larger than just in
FM. Within FM, you ca
Looking back at this again, I believe I'd go with putting the topic
info in a file by itself and then importing it as necessary under the
appropriate head.
Art
Art Campbell
art.campbell at gmail.com
"... In my opinion, there's nothing in this world beats a '52
Vincent and a redhe
Art and Richard both recommended the idea of insetting topic body text
between the headings in a container doc. My biggest qualm about using
container docs with all of the headings then insetting the body text is
the sheer number of insets.
I recently tried breaking my doc set into topic-size
Judy wrote:
> The challenge is how to best handle those topics that appear in more
> than 1 output, but at different heading levels--most commonly an H3 in
> the full manual becomes an H2 in the quickstarts.
>
> I've thought about:
> - Multiple conditionalized headings, but that would cause xre
Judy wrote:
> The challenge is how to best handle those topics that appear in more
> than 1 output, but at different heading levels--most commonly an H3 in
> the full manual becomes an H2 in the quickstarts.
>
> I've thought about:
> - Multiple conditionalized headings, but that would cause xr
meusers.com
> [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Judy
> Sent: Monday, June 01, 2009 9:26 AM
> To: framers at lists.frameusers.com
> Subject: Topic changes heading levels
>
> I'm using Tech. Comm. Suite ( FM8 ver. 8.0p277 & RH7 ver. 7.02.001) to
> g
Looking back at this again, I believe I'd go with putting the topic
info in a file by itself and then importing it as necessary under the
appropriate head.
Art
Art Campbell
art.campb...@gmail.com
"... In my opinion, there's nothing in this world beats a '52
Vincent and a redheade
; [mailto:framers-boun...@lists.frameusers.com] On Behalf Of Judy
> Sent: Monday, June 01, 2009 9:26 AM
> To: framers@lists.frameusers.com
> Subject: Topic changes heading levels
>
> I'm using Tech. Comm. Suite ( FM8 ver. 8.0p277 & RH7 ver. 7.02.001) to
> generate multiple u
mers-boun...@lists.frameusers.com
[mailto:framers-boun...@lists.frameusers.com] On Behalf Of Judy
Sent: Monday, June 01, 2009 9:26 AM
To: framers@lists.frameusers.com
Subject: Topic changes heading levels
I'm using Tech. Comm. Suite ( FM8 ver. 8.0p277 & RH7 ver. 7.02.001) to
generate
From: framers-boun...@lists.frameusers.com
[mailto:framers-bounces at lists.frameusers.com] On Behalf Of Judy
Sent: Monday, June 01, 2009 9:26 AM
To: framers at lists.frameusers.com
Subject: Topic changes heading levels
I'm using Tech. Comm. Suite ( FM8 ver. 8.0p277 & RH7 ver. 7.02.001
I'm using Tech. Comm. Suite ( FM8 ver. 8.0p277 & RH7 ver. 7.02.001) to
generate multiple user manuals (a full manual and 3 quickstarts) as well
as CHM Help files. (Windows XP SP3 if it matters.)
The challenge is how to best handle those topics that appear in more
than 1 output, but at differen
I'm using Tech. Comm. Suite ( FM8 ver. 8.0p277 & RH7 ver. 7.02.001) to
generate multiple user manuals (a full manual and 3 quickstarts) as well
as CHM Help files. (Windows XP SP3 if it matters.)
The challenge is how to best handle those topics that appear in more
than 1 output, but at differen
18 matches
Mail list logo
