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.
I'm resending this, as I'm pretty sure it didn't make the list. Apologies if
it's a repeat. Thanks. DB.
-----Original Message-----
From: Darren Barefoot
Sent: 12 November 2001 11:36
To: TECHWR-L
Subject: RE: Software Text Incorrect
I don't know if this solution has been mentioned, but here's my two cents:
For internationalization purposes, it is a good practice to actually store
all of your UI strings (button labels, window titles, error messages, etc)
in a database and call them at runtime. This means that when you need the UI
translated into, say, Senegalese, you just need to send the language
database to Dakar. Translators aren't routing through your code to find UI
strings.
This also means that writers can easily review these strings. We would
periodically check this database for new strings and review and correct them
without ever bothering the engineers. Of course, this is a job whose tedium
rivals indexing, but that's the easiest way to do it. Thanks. DB.
> -----Original Message-----
> From: TDean -at- envirosys -dot- com [mailto:TDean -at- envirosys -dot- com]
> Sent: 06 November 2001 21:27
> To: TECHWR-L
> Subject: Software Text Incorrect
>
<snip>
>
> I was just wondering how other writers handle this?
> Especially in a company where the software screens do not
> heed to any specifications on terms or styles, this is
> something that is frustrating. I read somewhere that the
> technical writer should not try to compensate for the
> software's shortcomings - if the documentation does not match
> the software, then the users get confused. I know I would.
>
> Tina Dean
>
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
---
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.
