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.
To repeat it: This checklist is intended to define how you, as a writer of
online documentation, will interact with the programmers of your project.
Preparation for Localisation
----------------------------
H) Urge the programmers to isolate every single word that will be
displayed and may be translated from their normal source code.
Many machine-readable files contain words that definitely should
not be translated, e.g. "showpage" as the last command in a
PostScript file. Not to mention that the program source code
itself is made up out of "words". For some platforms there are
tools that do the separation automatically.
How much help?
--------------
I) Discuss where context-sensitive help will be needed. Decide on
a consistent way to do it: Should <F1> show something about the
active window, control, menu or menu item? Should there be extra
help for every control or entry field, e.g., by those bubbles
called "tool tips" in Windows 95? This will have great impact on
the number of help topics you will write and on how much
information will remain for the paper manual.
Any additions or clarifications for this?
If you wish to receive the check list in its present unfinished form
(presently Version 0.2 dated 27-JUL-95), send an empty message to
onlchecklist -at- twh -dot- msn -dot- sub -dot- org
If you wish to join the Forum 95 mailing list, sent a message to
listserv -at- twh -dot- msn -dot- sub -dot- org -dot- the message should contain one or more of the
following lines: