Re: [Framers] Going bonkers with an x-ref format

[tammyvb]

Yep, I agree, but . . . I have punted for now. Any thoughts and/or
commiseration would be appreciated.

TVB

Tammy Van Boening
Tammy dot vanboening at spectrumwritingllc dot com
www.spectrumwritingllc.com

-Original Message-
From: Framers
<framers-bounces+tammyvb=spectrumwritingllc@lists.frameusers.com> On
Behalf Of Robert Lauriston
Sent: Wednesday, March 14, 2018 2:38 PM
To: An email list for people using Adobe FrameMaker software.
<framers@lists.frameusers.com>
Subject: Re: [Framers] Going bonkers with an x-ref format

I'd expect that kind of behavior if ChapterTitle were a reserved keyword in
FrameMaker or Acrobat. If that were the case, it might show up in the
ExtendScript documentation.

On Wed, Mar 14, 2018 at 1:35 PM,  <tamm...@spectrumwritingllc.com> wrote:
> OK, scratch what I thought worked. Even w/ the paragraph tags placed
BEFORE the ChapterTitle tag, I still get the same problem IF I try to
include the Chapter number in the x-ref. If I explicitly omit the chapter
number, then all is OK. I give. . . .for now, I am just going w/out the
Chapter number in the x-ref. I don't have enough time to figure this one
out, but if anyone has any ideas . . .
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com Visit the list's homepage at
http://www.frameusers.com Archives located at
http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Going bonkers with an x-ref format

[Robert Lauriston]

I'd expect that kind of behavior if ChapterTitle were a reserved
keyword in FrameMaker or Acrobat. If that were the case, it might show
up in the ExtendScript documentation.

On Wed, Mar 14, 2018 at 1:35 PM,   wrote:
> OK, scratch what I thought worked. Even w/ the paragraph tags placed BEFORE 
> the ChapterTitle tag, I still get the same problem IF I try to include the 
> Chapter number in the x-ref. If I explicitly omit the chapter number, then 
> all is OK. I give. . . .for now, I am just going w/out the Chapter number in 
> the x-ref. I don't have enough time to figure this one out, but if anyone has 
> any ideas . . .
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Going bonkers with an x-ref format

[tammyvb]

OK, scratch what I thought worked. Even w/ the paragraph tags placed BEFORE the 
ChapterTitle tag, I still get the same problem IF I try to include the Chapter 
number in the x-ref. If I explicitly omit the chapter number, then all is OK. I 
give. . . .for now, I am just going w/out the Chapter number in the x-ref. I 
don't have enough time to figure this one out, but if anyone has any ideas . . .

TVB

Tammy Van Boening
Tammy dot vanboening at spectrumwritingllc dot com
www.spectrumwritingllc.com

-Original Message-
From: Framers 
<framers-bounces+tammyvb=spectrumwritingllc@lists.frameusers.com> On Behalf 
Of Peter Gold
Sent: Wednesday, March 14, 2018 2:02 PM
To: An email list for people using Adobe FrameMaker software. 
<framers@lists.frameusers.com>
Subject: Re: [Framers] Going bonkers with an x-ref format

On Wed, Mar 14, 2018 at 2:36 PM, <tamm...@spectrumwritingllc.com> wrote:

> Tried that and no go. In frustration, I moved the two auto-numbered 
> tags so that they were BEFORE the ChapterTitle tag and not after and 
> voila - the x-refs now work, but this was a Hail Mary and for whatever 
> reason, it worked. Logically, however, I cannot understand why. I did 
> not think that FM x-refs were "location-dependent" in that sense. The 
> auto-numbered tags were explicitly placed in the files, not just 
> listed in the Paragraph catalogue.
> For now, I am going w/ this, but if anyone wants to provide an 
> explanation, I would love to understand.


​Glad you unearthed another solution gem.

Perhaps it's got to do with the accumulated length of the headings that are 
being concatenated​.
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com Visit the list's homepage at  
http://www.frameusers.com Archives located at 
http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Going bonkers with an x-ref format

[Peter Gold]

On Wed, Mar 14, 2018 at 2:36 PM,  wrote:

> Tried that and no go. In frustration, I moved the two auto-numbered tags so
> that they were BEFORE the ChapterTitle tag and not after and voila - the
> x-refs now work, but this was a Hail Mary and for whatever reason, it
> worked. Logically, however, I cannot understand why. I did not think that
> FM
> x-refs were "location-dependent" in that sense. The auto-numbered tags were
> explicitly placed in the files, not just listed in the Paragraph catalogue.
> For now, I am going w/ this, but if anyone wants to provide an explanation,
> I would love to understand.


​Glad you unearthed another solution gem.

Perhaps it's got to do with the accumulated length of the headings that are
being concatenated​.
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Going bonkers with an x-ref format

[tammyvb]

Tried that and no go. In frustration, I moved the two auto-numbered tags so
that they were BEFORE the ChapterTitle tag and not after and voila - the
x-refs now work, but this was a Hail Mary and for whatever reason, it
worked. Logically, however, I cannot understand why. I did not think that FM
x-refs were "location-dependent" in that sense. The auto-numbered tags were
explicitly placed in the files, not just listed in the Paragraph catalogue.
For now, I am going w/ this, but if anyone wants to provide an explanation,
I would love to understand.

Old Way:

ChapterNumber
ChapterTitle
FileName_PDF
FileName_OLH
Heading1s
Headings2s
Heading3s

New Way:

FileName_PDF
FileName_OLH
ChapterNumber
ChapterTitle
Heading1s
Headings2s
Heading3s

Tammy Van Boening
Tammy dot vanboening at spectrumwritingllc dot com
www.spectrumwritingllc.com

-Original Message-
From: Framers
<framers-bounces+tammyvb=spectrumwritingllc@lists.frameusers.com> On
Behalf Of Robert Lauriston
Sent: Wednesday, March 14, 2018 12:50 PM
To: An email list for people using Adobe FrameMaker software.
<framers@lists.frameusers.com>
Subject: Re: [Framers] Going bonkers with an x-ref format

What if you rename the ChapterTitle tag to something else, such as Heading0?

Years ago I switched from ChapterTitle > Heading1 > Heading2 ... to
Heading1 > Heading2 ... because of some problem with the ChapterTitle tag.

On Wed, Mar 14, 2018 at 11:14 AM,  <tamm...@spectrumwritingllc.com> wrote:
> For a current project, I have 30 FM books that are converted to PDFs 
> and then used to create a merged OLH system in ePub. There are links 
> scattered throughout every file in every book that are inter-book 
> links that are converted and maintained in the PDFs.  I have two 
> paragraph tags called FileName_PDF and FileName_OLH. These tags have 
> an autonumber format set to the name of the PDF file and the OLH TOC 
> entry accordingly, for example, Objects. PDF and Objects, and the 
> character tag is set to White.  I place these tags immediately after 
> the ChapterTitle tag on the first page of very chapter/file in a book. 
> Because they are white, the values do not show/are not visible in the
chapter/file.
>
> In the text of files, for an inter-book, x-ref, I use two formats, w/ 
> the format that uses the FileName_PDF conditionalized to Print_Only 
> and the format that uses the FileName_OLH set to OLH_Only. These links 
> are set to the following format:
>
> "<$paratext>" in <$paranum[FileName_PDF]>.
> "<$paratext>" in <$paranum[FileName_OLH]>.
>
> That way, in the PDF, the user will see something such as: For more 
> information, see "Blah" in Objects.PDF, while in the OLH, the user 
> will see something such as: For more information, see "Blah" in Objects.
>
> If the x-ref is to a Heading1, Heading2, Heading3, etc. tag, then the 
> text is displayed as expected in the example above; however, if the 
> x-ref is to a ChapterTitle, then I get only this: For more 
> information, see "Blah" in < > and no matter what, the FileName_PDF 
> value or the FileName_OLH value will not populate/be displayed, which 
> makes no sense as these values are indeed in the chapter. I thought it 
> had something to do w/ the fact that I was requesting to link just to 
> paratext and so I even set up a test x-ref format like this:
>
> Chapter <$chapnum>, "<$paratext>," in <$paranum[FileName_PDF]>, 
> but again, no joy.
>
> I am totally stumped. Why on earth would referencing a ChapterTitle 
> paragraph prevent an autonumber value from being displayed in an 
> x-ref? I must absolutely be able to reference a chapter title in this type
of x-ref.
> Any and all thoughts are sincerely appreciated.
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com Visit the list's homepage at
http://www.frameusers.com Archives located at
http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

Re: [Framers] Going bonkers with an x-ref format

[Robert Lauriston]

What if you rename the ChapterTitle tag to something else, such as Heading0?

Years ago I switched from ChapterTitle > Heading1 > Heading2 ... to
Heading1 > Heading2 ... because of some problem with the ChapterTitle
tag.

On Wed, Mar 14, 2018 at 11:14 AM,   wrote:
> For a current project, I have 30 FM books that are converted to PDFs and
> then used to create a merged OLH system in ePub. There are links scattered
> throughout every file in every book that are inter-book links that are
> converted and maintained in the PDFs.  I have two paragraph tags called
> FileName_PDF and FileName_OLH. These tags have an autonumber format set to
> the name of the PDF file and the OLH TOC entry accordingly, for example,
> Objects. PDF and Objects, and the character tag is set to White.  I place
> these tags immediately after the ChapterTitle tag on the first page of very
> chapter/file in a book. Because they are white, the values do not show/are
> not visible in the chapter/file.
>
> In the text of files, for an inter-book, x-ref, I use two formats, w/ the
> format that uses the FileName_PDF conditionalized to Print_Only and the
> format that uses the FileName_OLH set to OLH_Only. These links are set to
> the following format:
>
> "<$paratext>" in <$paranum[FileName_PDF]>.
> "<$paratext>" in <$paranum[FileName_OLH]>.
>
> That way, in the PDF, the user will see something such as: For more
> information, see "Blah" in Objects.PDF, while in the OLH, the user will see
> something such as: For more information, see "Blah" in Objects.
>
> If the x-ref is to a Heading1, Heading2, Heading3, etc. tag, then the text
> is displayed as expected in the example above; however, if the x-ref is to a
> ChapterTitle, then I get only this: For more information, see "Blah" in < >
> and no matter what, the FileName_PDF value or the FileName_OLH value will
> not populate/be displayed, which makes no sense as these values are indeed
> in the chapter. I thought it had something to do w/ the fact that I was
> requesting to link just to paratext and so I even set up a test x-ref format
> like this:
>
> Chapter <$chapnum>, "<$paratext>," in <$paranum[FileName_PDF]>, but
> again, no joy.
>
> I am totally stumped. Why on earth would referencing a ChapterTitle
> paragraph prevent an autonumber value from being displayed in an x-ref? I
> must absolutely be able to reference a chapter title in this type of x-ref.
> Any and all thoughts are sincerely appreciated.
___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com

[Framers] Going bonkers with an x-ref format

[tammyvb]

For a current project, I have 30 FM books that are converted to PDFs and
then used to create a merged OLH system in ePub. There are links scattered
throughout every file in every book that are inter-book links that are
converted and maintained in the PDFs.  I have two paragraph tags called
FileName_PDF and FileName_OLH. These tags have an autonumber format set to
the name of the PDF file and the OLH TOC entry accordingly, for example,
Objects. PDF and Objects, and the character tag is set to White.  I place
these tags immediately after the ChapterTitle tag on the first page of very
chapter/file in a book. Because they are white, the values do not show/are
not visible in the chapter/file. 

In the text of files, for an inter-book, x-ref, I use two formats, w/ the
format that uses the FileName_PDF conditionalized to Print_Only and the
format that uses the FileName_OLH set to OLH_Only. These links are set to
the following format:

"<$paratext>" in <$paranum[FileName_PDF]>.
"<$paratext>" in <$paranum[FileName_OLH]>.

That way, in the PDF, the user will see something such as: For more
information, see "Blah" in Objects.PDF, while in the OLH, the user will see
something such as: For more information, see "Blah" in Objects.

If the x-ref is to a Heading1, Heading2, Heading3, etc. tag, then the text
is displayed as expected in the example above; however, if the x-ref is to a
ChapterTitle, then I get only this: For more information, see "Blah" in < >
and no matter what, the FileName_PDF value or the FileName_OLH value will
not populate/be displayed, which makes no sense as these values are indeed
in the chapter. I thought it had something to do w/ the fact that I was
requesting to link just to paratext and so I even set up a test x-ref format
like this:

Chapter <$chapnum>, "<$paratext>," in <$paranum[FileName_PDF]>, but
again, no joy.

I am totally stumped. Why on earth would referencing a ChapterTitle
paragraph prevent an autonumber value from being displayed in an x-ref? I
must absolutely be able to reference a chapter title in this type of x-ref.
Any and all thoughts are sincerely appreciated.

TIA,

TVB


Tammy Van Boening
Tammy dot vanboening at spectrumwritingllc dot com
www.spectrumwritingllc.com



___

This message is from the Framers mailing list

Send messages to framers@lists.frameusers.com
Visit the list's homepage at  http://www.frameusers.com
Archives located at http://www.mail-archive.com/framers%40lists.frameusers.com/
Subscribe and unsubscribe at 
http://lists.frameusers.com/listinfo.cgi/framers-frameusers.com
Send administrative questions to listad...@frameusers.com