XREF bug with conditional text

[Everette, Dimi]

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






This communication (including any attachments) may contain privileged or confidential information of Polycom and is intended for a 
specific individual.  If you are not the intended recipient, you should delete this communication, including any attachments without 
reading or saving them in any manner,and you are hereby notified that any disclosure, copying, or distribution of this communication, 
or the taking of any action based on it, is strictly prohibited.
Please consider your environmental responsibility before printing this e-mail.


-----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, Technical Communicator & Localization Manager.
IAR Systems AB
Box 23051, Strandbodgatan 1
SE-750 23 Uppsala, SWEDEN
Mobile: +46 708 651088, Phone: +46 18 167894, Fax: +46 18 167838
E-mail: johan.anglemark at iar.com Website: www.iar.com
Twitter: www.twitter.com/iarsystems

_______________________________________________


You are currently subscribed to framers as dimi.everette at polycom.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/dimi.everette%40polycom.com

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