[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: framers@xxxxxxxxx, framers@xxxxxxxxxxxxxx
Subject: RE: Inconsistent Conditional text [DON'T FORGET COLOUR]
From: hedley_finger@xxxxxxxxxxx
Date: Wed, 26 Jun 2002 09:55:42 +1000
Sender: owner-framers@xxxxxxxxx
Sharon: An 'inconsistent indicators' error message may also mean that the same condition has a different COLOUR in different files, not just that indicators are visible in some files but invisible in others. So I would suggest that, when importing condition formats you also import colours. The suggestion to import conditions from every generated and non-generated file in a book to a separate control repository whence they can be imported back into the entire book is a good one -- just remember to import the colours, too. In fact at MYOB Australia we use a condition control file to which writers must add any new condition definitions and then import them throughout a book. The control file is a table with columns as follows: Comment, Name of condition, Current status, and Final status. The Current status column contains the name of the condition to which the condition format itself has also been applied. Thus, you can see at a glance which conditions are currently visible and which hidden. The Final status column just contains either the word Visible or Hidden to indicate to which state each condition SHOULD be set to customize the final deliverable. Regards, Hedley -- Hedley Finger Technical Communications/Technical communicator and FrameMaker mentor MYOB Australia <http://www.myob.com.au/> P.O. box 371 Blackburn VIC 3130 Australia 12 Wesley Court Tally Ho Business Park East Burwood VIC 3151 Australia <mailto:hedley_finger@myob.com.au> Tel. +61 3 9222 9992 x 7421, Mob. (cell) +61 412 461 558 (C) MYOB Limited 2002 ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **