Conditional Text and cross-references

2005-11-29 Thread rebecca officer
Hi Anita

We saw exactly this behaviour and decided it happened when our xref format 
included the "Default para font" tag. For example, we used a paragraph format 
to turn on bold for part of the xref text, then used default para font to go 
back to normal. So we bypassed the problem by using a tag that specifically 
turned bold off, that otherwise had everything set to "As is". Works fine.

Cheers, Rebecca

>>> "Anita Burstein"  28/11/05 20:31 >>>
Hi list!
I'm using FrameMaker 6.0.

I have a book with many conditions in it. Within the conditional text, there 
are cross-references. Some of the cross-references are to text marked with the 
same conditions and therefore shown at the same time. Some of the 
cross-references are to text that is unconditional, so that the cross-reference 
text to a heading, etc. might be hidden. 

The cross-references are formatted to show the heading text and page number.

Here's my problem: When I show all conditions and update the cross-references, 
the page numbers are automatically updated, but they lose their condition tag. 
When I then hide the conditions, the page number still shows, because it became 
unconditional. (If I manually update the cross-reference, it will pick up the 
condition again.)

Example:
"For more information, refer to Starting your System on page 23." ("Starting 
your System on page 23" is the cross-reference)
This entire sentence can be hidden with conditional text. However, when I 
updated cross-references with all conditions showing, "on page 23" remains 
unconditional and therefore shows when I hide the conditions.

This seems to happen consistently to the same cross-references, although I 
cannot seem to find a pattern across my book.

Thanks in advance for any help.

Anita Burstein
Technical Documentation, Product Marketing
NICE Systems Ltd., Israel
(T) (09) 775 3794
(F) (09) 775 3353
Anita.Burstein at nice.com <mailto:Anita.Burstein at nice.comwww.nice.com> 
www.nice.com 



NOTICE: This message contains privileged and confidential
information intended only for the use of the addressee
named above. If you are not the intended recipient of
this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it.
If you have received this message in error please
notify Allied Telesyn Research Ltd immediately.
Any views expressed in this message are those of the
individual sender, except where the sender has the
authority to issue and specifically states them to
be the views of Allied Telesyn Research.



Conditional Text and cross-references

2005-11-29 Thread hedley.fin...@myob.com
An alternative to typing  or  is to 
type , which does the same job.**  Have you tried these alternatives to 
see if they fix the problem with cross-references?

Hedley

**  The second alternative contains the blind Peter, i.e. the backwards 
facing P, just in case it comes out as some other character.

--
Hedley Finger
Technical Communications Tools & Processes Specialist
MYOB Australia 
P.O. box 371   Blackburn VIC 3130   Australia
12 Wesley Court   Tally Ho Business Park   East Burwood VIC 3151 Australia

Tel. +61 3 9222 9992 x 7421,   Mob. (cell) +61 412 461 558

? MYOB Technology Pty Ltd 2005



Conditional Text and cross-references

2005-11-29 Thread Anita Burstein
Thanks Rebecca,
I'll give it a try, but since it seemed random to me and I have many, many 
files to update, only time will tell.
Thanks again for the good advice! 


Anita Burstein
Technical Documentation, Product Marketing
NICE Systems Ltd., Israel
(T) (09) 775 3794
(F) (09) 775 3353
Anita.Burstein at nice.com
www.nice.com


-Original Message-
From: Peter Gold [mailto:pe...@knowhowpro.com] 
Sent: Monday, November 28, 2005 11:44 PM
To: rebecca officer
Cc: framers at lists.frameusers.com; Anita Burstein
Subject: Re: Conditional Text and cross-references

Hi, Rebecca:

At 10:28 AM +1300 11/29/05, rebecca officer wrote:
>Hi Anita
>
>We saw exactly this behaviour and decided it happened when our xref 
>format included the "Default para font" tag. For example, we used a 
>paragraph format to turn on bold for part of the xref text, then used 
>default para font to go back to normal. So we bypassed the problem by 
>using a tag that specifically turned bold off, that otherwise had 
>everything set to "As is". Works fine.

This has got to be one of the all-time most-obscure FrameMaker Trivial Pursuit 
discoveries ever made!! Congratulations!
--
Regards,

Peter Gold
KnowHow ProServices
peter at knowhowpro.com





Conditional Text and cross-references

2005-11-28 Thread Anita Burstein
Hi list!
I'm using FrameMaker 6.0.

I have a book with many conditions in it. Within the conditional text, there 
are cross-references. Some of the cross-references are to text marked with the 
same conditions and therefore shown at the same time. Some of the 
cross-references are to text that is unconditional, so that the cross-reference 
text to a heading, etc. might be hidden. 

The cross-references are formatted to show the heading text and page number.

Here's my problem: When I show all conditions and update the cross-references, 
the page numbers are automatically updated, but they lose their condition tag. 
When I then hide the conditions, the page number still shows, because it became 
unconditional. (If I manually update the cross-reference, it will pick up the 
condition again.)

Example:
"For more information, refer to Starting your System on page 23." ("Starting 
your System on page 23" is the cross-reference)
This entire sentence can be hidden with conditional text. However, when I 
updated cross-references with all conditions showing, "on page 23" remains 
unconditional and therefore shows when I hide the conditions.

This seems to happen consistently to the same cross-references, although I 
cannot seem to find a pattern across my book.

Thanks in advance for any help.

Anita Burstein
Technical Documentation, Product Marketing
NICE Systems Ltd., Israel
(T) (09) 775 3794
(F) (09) 775 3353
Anita.Burstein at nice.com <mailto:Anita.Burstein at nice.comwww.nice.com> 
www.nice.com


-- next part --
An HTML attachment was scrubbed...
URL: 
http://lists.frameusers.com/pipermail/framers/attachments/20051128/212088f1/attachment.html
 


Conditional Text and cross-references

2005-11-28 Thread Shlomo Perets
Anita,

You wrote:

>I'm using FrameMaker 6.0.
>
>I have a book with many conditions in it. Within the conditional text,
>there are cross-references. Some of the cross-references are to text
>marked with the same conditions and therefore shown at the same time.
>Some of the cross-references are to text that is unconditional, so
>that the cross-reference text to a heading, etc. might be hidden.
>
>The cross-references are formatted to show the heading text and page number.
>
>Here's my problem: When I show all conditions and update the
>cross-references, the page numbers are automatically updated, but they
>lose their condition tag. When I then hide the conditions, the page
>number still shows, because it became unconditional. (If I manually
>update the cross-reference, it will pick up the condition again.)
>
>Example:
>"For more information, refer to Starting your System on page 23."
>("Starting your System on page 23" is the cross-reference)
>This entire sentence can be hidden with conditional text. However,
>when I updated cross-references with all conditions showing, "on page
>23" remains unconditional and therefore shows when I hide the
>conditions.
>
>This seems to happen consistently to the same cross-references,
>although I cannot seem to find a pattern across my book.

Sounds similar to the bug where one of two consecutive character formats 
present in a cross-reference format is removed when you Update References 
through a book.

Please see Adobe tech note #317963,  "Updating a FrameMaker 6.0 or 5.x Book 
File Removes Character Formats in Cross-References" 
--http://www.adobe.com/support/techdocs/317963.html -- it may have 
information related to the problem you experience. This bug is not specific 
to FrameMaker 6 or 5.x, and is encountered in FrameMaker 7.x as well.


Shlomo Perets

MicroType, http://www.microtype.com * ToolbarPlus Express for FrameMaker
FrameMaker/Acrobat training & consulting * FrameMaker-to-Acrobat 
TimeSavers/Assistants
Template Design, Single Sourcing, FM-to-PDF & Technical Indexing seminars






Conditional Text and cross-references

2005-11-28 Thread Peter Gold
Hi, Rebecca:

At 10:28 AM +1300 11/29/05, rebecca officer wrote:
>Hi Anita
>
>We saw exactly this behaviour and decided it happened when our xref 
>format included the "Default para font" tag. For example, we used a 
>paragraph format to turn on bold for part of the xref text, then 
>used default para font to go back to normal. So we bypassed the 
>problem by using a tag that specifically turned bold off, that 
>otherwise had everything set to "As is". Works fine.

This has got to be one of the all-time most-obscure FrameMaker 
Trivial Pursuit discoveries ever made!! Congratulations!
-- 
Regards,

Peter Gold
KnowHow ProServices
peter at knowhowpro.com



Conditional Text and cross-references

2005-11-28 Thread Grant Hogarth
Huh.  I thought this was on the "expert" test, under "how to hack FM".

I've been using that for years to tweak kearning/tracking.

OTOH, I've never figured out how to get embedded formatting to work for
generated marker lists.
   EXAMPLE: 
  Marker Type: ChangedContent
  Marker Text: Heading\:note on what changed.
Generating a List of markers always treats the marker Text as text, 
while generating an Index of markers reads the formatting and applies
it.

Grant

-Original Message-
From: framers-bounces+grant.hogarth=reuters@lists.frameusers.com
[mailto:framers-bounces+grant.hogarth=reuters.com at lists.frameusers.com]
On Behalf Of Peter Gold
Sent: Monday, November 28, 2005 2:44 PM
To: rebecca officer
Cc: framers at lists.frameusers.com; Anita.Burstein at nice.com
Subject: Re: Conditional Text and cross-references


Hi, Rebecca:

At 10:28 AM +1300 11/29/05, rebecca officer wrote:
>Hi Anita
>
>We saw exactly this behaviour and decided it happened when our xref
>format included the "Default para font" tag. For example, we used a 
>paragraph format to turn on bold for part of the xref text, then 
>used default para font to go back to normal. So we bypassed the 
>problem by using a tag that specifically turned bold off, that 
>otherwise had everything set to "As is". Works fine.

This has got to be one of the all-time most-obscure FrameMaker 
Trivial Pursuit discoveries ever made!! Congratulations!
-- 
Regards,

Peter Gold
KnowHow ProServices
peter at knowhowpro.com ___


You are currently subscribed to Framers as Grant.Hogarth at reuters.com.

To unsubscribe send a blank email to 
framers-unsubscribe at lists.frameusers.com
or visit
http://lists.frameusers.com/mailman/options/framers/grant.hogarth%40reut
ers.com

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


To find out more about Reuters visit www.about.reuters.com

Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
Reuters Ltd.