TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:RE: FONT STANDARDS From:Maritza van den Heuvel <MaritzaV -at- stt-global -dot- com> To:" (TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM)" <TECHWR-L -at- LISTS -dot- RAYCOMM -dot- COM> Date:Fri, 13 Feb 2004 22:37:28 +0200
Erid Dunn wrote:
And then you MIGHT change your mind. :)
So, tag all the different instances using styles that identify the
function not the formatting. So when you DO change your mind, the
formatting can easily be changed throughout.
Or, use SGML/XML with tags identifying the different items so that they
can be formatted according to their type. (or NOT.)
Eric L. Dunn
Senior Technical Writer
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That's where formatting styles come into it. If your tool is styles-based,
you hypothetically create styles for Buttons and Menus, Special Keys, Code
or whatever and apply these to your text. And then when you change your
mind, you simply update the style and the changes update wherever the styles
are used. :-)
