XREF bug with conditional text

[Jeff Coatsworth]

The more people who complain about it, the better the chance of it getting fixed - use https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform to show your displeasure :>) 

-----Original Message-----
From: framers-bounces at lists.frameusers.com [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Johan Anglemark
Sent: Thursday, October 13, 2011 3:00 AM
To: framers at lists.frameusers.com
Subject: Re: XREF bug with conditional text

That's good to hear. Unfortunately, in our case, the xrefs are seldom 
broken, because they lead to other texts that are indeed present in the 
book, but hidden from view. So instead I will get texts in my files like:

"To avoid this behavior, include the optional header file.page134"

where "page134" of course is the part of longer, hidden text with a 
cross-reference, where everything except the page referral is correctly 
hidden. And because the text referred to is present (but also hidden) on 
page 134, Frame doesn't regards the link as broken and doesn't alert me 
to it.

Regards,

Johan

On 2011-10-12 22:47, Everette, Dimi wrote:
> Johan, I just experienced this bug with one of my chapters too. It
> was the first time I'd worked with this particular book. One of the
> chapters has dozens of xrefs that are within conditional text that is
> hidden, so I get dozens of "broken xref" messages when I generate.
> With my books, if I use the Find tool and FrameMaker does not find
> any missing xrefs, I consider it a non-issue and ignore the error
> messages.
>
> Regards, Dimi
>
>
> Dimi Everette, Sr. Technical Writer, Video Information Design 6500
> River Place Blvd., Bldg. 6, Austin, TX 78730  | t: 512.372.6988 | f:
> 512.372.7001
>
> -----Original Message----- From: framers-bounces at lists.frameusers.com
> [mailto:framers-bounces at lists.frameusers.com] On Behalf Of Johan
> Anglemark Sent: Tuesday, October 11, 2011 4:01 AM To:
> framers at lists.frameusers.com Subject: XREF bug with conditional text
>
> This is a bug we've experienced at least since Frame 8 and we've
> finally tired of it (we're using Frame 10 now). I have found nothing
> when googling or in the Adobe Support forums.
>
> The bug is simple to describe: For cross-reference formats that use
> the <Default ¶ Font>  tag, if a cross-reference is tagged as
> conditional, the part of the cross-reference that falls outside of
> the<Font tag><Default ¶ Font>  pair sometimes loses the
> conditioning.
>
> For example, I have an XREF format defined as:
>
> <Reference><$paratext><Default ¶ Font>, page<$pagenum>
>
> A cross-reference might look like this:
>
> See CHAPTER ABOUT FEATURE A, page 66.
>
> Because this cross-reference points to a chapter that is only
> included for products with feature A, we have given it the condition
> "A only" which is set to hide when we generate the documentation for
> product B.
>
> However, after updating the book, ", page 66" will be without the
> condition tag and thus visible in all PDF versions. Apparently,
> sometimes the<Default ¶ Font>  tag terminates the condition and not
> just the font tag.
>
> Has anyone else seen this? Is there a workaround? A fix?
>
> Johan


-- 
Johan Anglemark

Tel: 0708-65 10 88

_______________________________________________


You are currently subscribed to framers as jeff.coatsworth at jonassoftware.com.

Send list messages to framers at lists.frameusers.com.

To unsubscribe send a blank email to
framers-unsubscribe at lists.frameusers.com
or visit http://lists.frameusers.com/mailman/options/framers/jeff.coatsworth%40jonassoftware.com

Send administrative questions to listadmin at frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.