, March 14, 2018 2:38 PM
To: An email list for people using Adobe FrameMaker software.
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
ExtendS
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
> t
ch 14, 2018 2:02 PM
To: An email list for people using Adobe FrameMaker software.
Subject: Re: [Framers] Going bonkers with an x-ref format
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 C
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
Behalf Of Robert Lauriston
Sent: Wednesday, March 14, 2018 12:50 PM
To: An email list for people using Adobe FrameMaker software.
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 Ch
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
