Correct, still in Frame. Thanks for your reply, Steve.
What I mean is, if you create an x-ref --> "Installing the Client" on page 82 -- and condition it Print Only. Then update the book file (in Frame) and show Help Only (i.e. hide Print Only). All or part of the x-ref will become unconditioned, so you might see only "on page 82" or the whole x-ref. In our attempt to resolve the issue, we realized that Webworks omits the page number automatically, so we weren't sure what purpose "HiddenOnline" (a character style) serves in the x-ref definition created by the designer: </><HiddenOnline>\`<$paratext><HiddenOnline>\' on page\ <$pagenum></> As I said, this template is 8 years old. We have never seen this behavior before and it occurs in one project only. It suggests some kind of file corruption. I'm not sure if the writer tried porting the content into a fresh file as a potential fix yet. Thanks again! Danny On Fri, Sep 3, 2010 at 7:58 PM, Steve Johnson <chinask...@gmail.com> wrote: > What do you mean by this: > > " e.g. "Installing the Client" on page 82 -- is conditioned Print Only. > Update the book file and show Help Only. You may get 'on page 82' or the > entire x-ref now unconditional. The problem appears to be cumulative." > > You mean you're still in Frame correct, and not processing the help? > > If so then you probably have two cross references, one for the heading > and one for the page number and your condition tag ends with the > heading. > > And this doesn't mean much: > > "> Some complexity was engineered into the the x-ref definition (by a > wizard > > long ago gone), so that Webworks could omit page references," > > Please explain. WebWorks will omit page number references all on its > own. You don't need "a wizard" to do that. > > On Thu, Sep 2, 2010 at 4:44 PM, Danny Lombardi <dannylomba...@gmail.com> > wrote: > > Hi folks, > > > > Parts of our x-refs lose their conditioning whenever we update the book. > > Does this ring any bells for anyone? > > > > e.g. > > "Installing the Client" on page 82 -- is conditioned Print Only. > > Update the book file and show Help Only. You may get 'on page 82' or the > > entire x-ref now unconditional. The problem appears to be cumulative. The > > more you update, the worse the problem gets. > > > > We generate many single-source projects, but only one has ever exhibited > > this problem. Same template. The x-ref definitions are the same across > the > > projects. Interestingly, it is our biggest document (of course!). > > > > Some complexity was engineered into the the x-ref definition (by a wizard > > long ago gone), so that Webworks could omit page references, but I > thought > > I'd put this out there to see if it's a known issue in Frame rather than > a > > result of some corruption in the file itself. > > > > FrameMaker 7.0 on XP > > > > Many thanks, > > Danny Lombardi > > Open Text > > _______________________________________________ > > > > > > You are currently subscribed to framers as dr_go...@pobox.com. > > > > Send list messages to fram...@lists.frameusers.com. > > > > To unsubscribe send a blank email to > > framers-unsubscr...@lists.frameusers.com > > or visit > http://lists.frameusers.com/mailman/options/framers/dr_gonzo%40pobox.com > > > > Send administrative questions to listad...@frameusers.com. Visit > > http://www.frameusers.com/ for more resources and info. > > > > > > -- > ============ > Steve Johnson, dr_go...@pobox.com > _______________________________________________ You are currently subscribed to framers as arch...@mail-archive.com. Send list messages to fram...@lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscr...@lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to listad...@frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
