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.
We don't need to, because the UI designers have already left room for
the localized menu, button, dialog and other text that is going to be
in the localized SW. Essentially, what we are doing in the docs is
the same thing that is done to localize the SW. The end result looks
the same as if we had done screen caps of the localized SW, except
that they only see the text that relates to the instruction that is
being delivered (we don't replace all the text we blank, just what is
needed for the figure; in some cases, the same graphic may be used in
multiple places with different text superimposed to make different
The user receives docs that are localized to match the SW they
receive. In markets where the user has a choice of which language SW
to install, the matching localized readme documentation and help are
installed with the SW.
On Tue, Mar 1, 2011 at 10:37 AM, Bill Swallow <techcommdood -at- gmail -dot- com> wrote:
> How do you account for language expansion using this model? Do your
> varying locale users obtain an English copy of the application or a
> translated version, and what is their experience like when going from
> mock-ups to the actual application?
> On Tue, Mar 1, 2011 at 1:21 PM, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
>> For screen caps we blank the text entirely,
>> and if necessary superimpose new text to replace what was on the
>> screen cap. Added text is external references to XML that is
>> localized along with the rest of the document.
> Bill Swallow
> Twitter: @techcommdood
> Blog: http://techcommdood.com
> LinkedIn: http://www.linkedin.com/in/techcommdood
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-