Re: Typographical treatment of GUI components

[eric -dot- dunn -at- ca -dot- transport -dot- bombardier -dot- com]

Here's an option: Apply a character format to all GUI component names. Then you
can ignore the question and get on with work until it really matters. When the
comittee/person in authority comes up with a ruling, change the format to
whatever they desire. If there is no concensus, print some pages out with
different formatting conventions to make a decision. Also, you can change the
way it's done on-line vs print by changing the format.

Use variables or crossreferences and you can also ensure that all GUI components
are consistently named. If any change, changing the name in one place will
change all instances in the doc set.

Eric L. Dunn



^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

NEED TO PUBLISH FRAMEMAKER CONTENT ONLINE? "Mustang" is a NEW single
sourcing tool for FrameMaker that lets you easily publish your content
online. No macro language required! http://www.ehelp.com/techwr-l3

Mercer University's online MS Program in Technical Communication Management:
Preparing leaders of tomorrow's technical communication organizations today.
See www.mercer.edu/mstco or write George Hayhoe at hayhoe_g -at- mercer -dot- edu -dot- 

---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.