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.
<< What I'm proposing is that a separate complete help is created for
each language with the same MapID number used for the same topic in
each language and that the reference to the correct CHM file is
passed through some type of variable to each application screen so
that the number is retained, just referenced against a different
compiled help.
Not being a programmer, I'd like to know if I'm coming from left
field on this, and what other issues had to be dealt with in this
translation process. >>
I believe your strategy to use the same MapID numbers is right on. Where you
go from there depends on how the multiple language program versions are
going to be distributed.
If you are going to create and distribute an install CD for each language,
there is no additional work to do for each version, as far as calling the
Help file from the program is concerned. (I would still give each .chm file
a unique name - see below)
However, let's say you will have one CD that contains multiple language
program versions, as well as multiple .chm files - one for each language.
The install could contain a screen for the user to select which particular
language version they want to install. The installation for each language
version would also install the respective .chm file.
Now, because you used the same MapIDs for each language version, you saved
yourself a LOT of work that won't have to be repeated for each language .chm
file. To lessen confusion, give each .chm file a unique name that indicates
the language it supports, ex: productnamegerman.chm,
productnamejapanese.chm, productnameitalian.chm, etc. All your programmers
will have to do is modify the .chm file name that gets called from the
application for each language program version.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY. http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by SOLUTIONS, Conferences and Seminars for Communicators
Publications Management Clinic, TECH*COMM 2001 Conference, and more http://www.SolutionsEvents.com or 800-448-4230
---
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.
