IX generation question restated

[Harold Winberg]

Earlier message was:

 

Dear Framers

 

We are entering a $paranum for both TOC and index (IX) entities. It
works, however, it applies the most recent autonumber format not the one
specifically assigned to the paragraph tag.

 

Hopefully more clearly stated:

 

 

We are trying to count work packages (chapters-files)(WP 0001 etc) using
a specific autonum assigned to the WP Number paragraph tag. This tag is
at the beginning of each document. The problem that we are encountering
is that any autonum occurrence that is previous to the TOC tag or IX
marker is reflected in the respective generated files instead of the WP
Number assignment. The autonum counters n, n+ etc. work. That is not
the issue. We want the WP Number assignment to carry into the TOC and IX
as opposed to any autonum occurrence that happens to be previous to the
TOC tag/IX marker

___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Re: IX generation question restated

[Rick Quatro]

Hi Harold,

The $paratag[FormatName] building blocks work in cross-references, but they 
don't work in indexes or tables of contents.

Rick Quatro
Carmen Publishing
585-659-8267
www.frameexpert.com



 Earlier message was:

 Dear Framers

 We are entering a $paranum for both TOC and index (IX) entities. It
 works, however, it applies the most recent autonumber format not the one
 specifically assigned to the paragraph tag.

 Hopefully more clearly stated:

 We are trying to count work packages (chapters-files)(WP 0001 etc) using
 a specific autonum assigned to the WP Number paragraph tag. This tag is
 at the beginning of each document. The problem that we are encountering
 is that any autonum occurrence that is previous to the TOC tag or IX
 marker is reflected in the respective generated files instead of the WP
 Number assignment. The autonum counters n, n+ etc. work. That is not
 the issue. We want the WP Number assignment to carry into the TOC and IX
 as opposed to any autonum occurrence that happens to be previous to the
 TOC tag/IX marker

___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

RE: IX generation question restated

[Combs, Richard]

Harold Winberg restated the problem:
 
 We are trying to count work packages (chapters-files)(WP 0001 
 etc) using a specific autonum assigned to the WP Number 
 paragraph tag. This tag is at the beginning of each document. 
 The problem that we are encountering is that any autonum 
 occurrence that is previous to the TOC tag or IX marker is 
 reflected in the respective generated files instead of the WP 
 Number assignment. The autonum counters n, n+ etc. work. 
 That is not the issue. We want the WP Number assignment to 
 carry into the TOC and IX as opposed to any autonum 
 occurrence that happens to be previous to the TOC tag/IX marker

Well, today is my Monday, so I'm still not getting it -- especially the
autonum occurrence that happens to be previous to the TOC tag/IX
marker part. :-} 

But it sounds like you're saying that each FM file in the book is a work
package, identified by a WP Number pgf, which has an autonumber that
should appear in the TOC and IX. Assuming you're using FM6 or newer, why
not use the Chapter Number variable ($chapnum) or, if that's being
used for something else, the Volume Number variable ($volnum) instead
of pre-FM6 autonum counters? 

See the manual chapter (or help topics) on TOCs and Indexes for info on
editing the TOC and IX flows to include one of these variables in the
generated files. It's fairly straightforward. For instance, in the ref
page IX flow, there's an IndexIX pgf that contains the page number
variable ($pagenum). To index by work package instead of page, replace
that variable with $chapnum or $volnum, whichever you decide to use
for the work package numbering. 

HTH!
Richard


--
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
--
rgcombs AT gmailDOTcom
303-777-0436
--




___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

Re: IX generation question restated

[Peter Gold]

 Harold Winberg restated the problem:

   We are trying to count work packages (chapters-files)(WP 0001
   etc) using a specific autonum assigned to the WP Number
   paragraph tag. This tag is at the beginning of each document.
   The problem that we are encountering is that any autonum
   occurrence that is previous to the TOC tag or IX marker is
   reflected in the respective generated files instead of the WP
   Number assignment. The autonum counters n, n+ etc. work.
   That is not the issue. We want the WP Number assignment to
   carry into the TOC and IX as opposed to any autonum
   occurrence that happens to be previous to the TOC tag/IX marker

Hi, Harold:

It's not clear what you're really after. When you say count work
packages, does that mean you want a list of them all, or just the
total, the work-package number as part of each TOC entry and as part
of each index entry, or something else?

If I understand your request correctly, this could work for you:

If you've defined the TOC-suffix paragraph formats with autonumber
formats, then the numbers reflect exactly what you describe - each TOC
entry counter is influenced by its predecessor.

* For the TOC: to capture the source paragraph's autonumber, in the
Table of Contents Specification on the TOC reference page, find the
example line for the workpackage paragraph - something like
workpackageTOC. Add the building block $paranum[workpackage] before
the $paratext building block and regenerate from the book file. TOC
entries will capture the workpackage paragraph's autonumber for each
occurrence of the workpackage paragraph throughout the book. Add the
$paranum[workpackage] building block before $pagenum on every
example line whose entry you want the workpackage number to precede
the entry.

* For the index: to capture the workpackage autonumber for every index
entry, add  $paranum[workpackage] before $pagenum of the IndexIX
example paragraph in the Index Specification on the index reference
page and regenerate. As far as I know, there's no way to capture the
autonumber for a specific index level (Level1IX, Level2IX, etc.). It's
all entries or none.

HTH

If you want
Regards,

Peter
___
Peter Gold
KnowHow ProServices
___


You are currently subscribed to Framers as [EMAIL PROTECTED]

Send list messages to [EMAIL PROTECTED]

To unsubscribe send a blank email to 
[EMAIL PROTECTED]
or visit 
http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com

Send administrative questions to [EMAIL PROTECTED] Visit
http://www.frameusers.com/ for more resources and info.

IX generation question restated

[Rick Quatro]

Hi Harold,

The $paratag[FormatName] building blocks work in cross-references, but they 
don't work in indexes or tables of contents.

Rick Quatro
Carmen Publishing
585-659-8267
www.frameexpert.com



> Earlier message was:
>
> Dear Framers
>
> We are entering a $paranum for both TOC and index (IX) entities. It
> works, however, it applies the most recent autonumber format not the one
> specifically assigned to the paragraph tag.
>
> Hopefully more clearly stated:
>
> We are trying to count work packages (chapters-files)(WP 0001 etc) using
> a specific autonum assigned to the WP Number paragraph tag. This tag is
> at the beginning of each document. The problem that we are encountering
> is that any autonum occurrence that is previous to the TOC tag or IX
> marker is reflected in the respective generated files instead of the WP
> Number assignment. The autonum counters ,  etc. work. That is not
> the issue. We want the WP Number assignment to carry into the TOC and IX
> as opposed to any autonum occurrence that happens to be previous to the
> TOC tag/IX marker

IX generation question restated

[Combs, Richard]

Harold Winberg restated the problem:

> We are trying to count work packages (chapters-files)(WP 0001 
> etc) using a specific autonum assigned to the WP Number 
> paragraph tag. This tag is at the beginning of each document. 
> The problem that we are encountering is that any autonum 
> occurrence that is previous to the TOC tag or IX marker is 
> reflected in the respective generated files instead of the WP 
> Number assignment. The autonum counters ,  etc. work. 
> That is not the issue. We want the WP Number assignment to 
> carry into the TOC and IX as opposed to any autonum 
> occurrence that happens to be previous to the TOC tag/IX marker

Well, today is my Monday, so I'm still not getting it -- especially the
"autonum occurrence that happens to be previous to the TOC tag/IX
marker" part. :-} 

But it sounds like you're saying that each FM file in the book is a work
package, identified by a WP Number pgf, which has an autonumber that
should appear in the TOC and IX. Assuming you're using FM6 or newer, why
not use the Chapter Number variable (<$chapnum>) or, if that's being
used for something else, the Volume Number variable (<$volnum>) instead
of pre-FM6 autonum counters? 

See the manual chapter (or help topics) on TOCs and Indexes for info on
editing the TOC and IX flows to include one of these variables in the
generated files. It's fairly straightforward. For instance, in the ref
page IX flow, there's an IndexIX pgf that contains the page number
variable (<$pagenum>). To index by work package instead of page, replace
that variable with <$chapnum> or <$volnum>, whichever you decide to use
for the work package numbering. 

HTH!
Richard


--
Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
303-223-5111
--
rgcombs AT gmailDOTcom
303-777-0436
--

IX generation question restated

[Peter Gold]

> Harold Winberg restated the problem:
>
>  > We are trying to count work packages (chapters-files)(WP 0001
>  > etc) using a specific autonum assigned to the WP Number
>  > paragraph tag. This tag is at the beginning of each document.
>  > The problem that we are encountering is that any autonum
>  > occurrence that is previous to the TOC tag or IX marker is
>  > reflected in the respective generated files instead of the WP
>  > Number assignment. The autonum counters ,  etc. work.
>  > That is not the issue. We want the WP Number assignment to
>  > carry into the TOC and IX as opposed to any autonum
>  > occurrence that happens to be previous to the TOC tag/IX marker

Hi, Harold:

It's not clear what you're really after. When you say "count work
packages," does that mean you want a list of them all, or just the
total, the work-package number as part of each TOC entry and as part
of each index entry, or something else?

If I understand your request correctly, this could work for you:

If you've defined the TOC-suffix paragraph formats with autonumber
formats, then the numbers reflect exactly what you describe - each TOC
entry counter is influenced by its predecessor.

* For the TOC: to capture the source paragraph's autonumber, in the
Table of Contents Specification on the TOC reference page, find the
example line for the workpackage paragraph - something like
workpackageTOC. Add the building block <$paranum[workpackage]> before
the <$paratext> building block and regenerate from the book file. TOC
entries will capture the workpackage paragraph's autonumber for each
occurrence of the workpackage paragraph throughout the book. Add the
<$paranum[workpackage]> building block before <$pagenum> on every
example line whose entry you want the workpackage number to precede
the entry.

* For the index: to capture the workpackage autonumber for every index
entry, add  <$paranum[workpackage]> before <$pagenum> of the IndexIX
example paragraph in the Index Specification on the index reference
page and regenerate. As far as I know, there's no way to capture the
autonumber for a specific index level (Level1IX, Level2IX, etc.). It's
all entries or none.

HTH

If you want
Regards,

Peter
___
Peter Gold
KnowHow ProServices