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.
> From: Julie <nobozos -at- SOUND -dot- NET>
> Make them change it, or do what I did, and learn how to change it
> Most programmers that I've worked with were willing to show me how to
> with source code control and how to read code if I would change stuff
> that for them.
In this case, it would be a little trickier than just editing source code,
as stuff like dialog text is usually not in the source code itself, but in
the resource file. You use a resource editor rather than a text editor to
change it. This is actually easier than hunting through the source code,
but it's an additional tool that must be learned.
Which is not to say that I don't think it would be productive for writers
to learn and to be given the opportunity to do this. Most programmers
shouldn't be allowed anywhere near human-readable text (and I say this as a