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.
Subject:UK/US English - What to do? From:Scott Browne <sbrowne -at- UNICOMP -dot- NET> Date:Fri, 7 May 1999 16:38:04 -0500
I've searched the archives and didn't find this particular dilemma
Our company has already decided on a course of action, but I thought I
would throw this out as a new topic for discussion and to give you
something to think about.
We have made a deal with a French software company to absorb/merge one of
their products into ours and do all the selling, marketing, and future
development for them. (They were tired of doing it themselves).
The software package, although developed in France, is designed in English
(menus, dialog boxes, etc.)
British English spellings were used in the interface. No documentation
currently exists for this application.
Because this product will be marketed to an American audience, should the
docs use US English spellings, or should it use the same UK English
spellings which the user will actually see on the interface?
For example, one item is labelled the "Colours Palette". Should the docs
"To access the Colours Palette, click Display>Colours Palette."
or should it read:
"To access the Color Palette, click Display>Color Palette." (even though
it's spelled the other way on the screen).
If the latter choice is made, I sincerely doubt a user will say to
himself, "Hmmm, I don't see the 'Color Palette' option on the Display
menu...all I can find is one called 'Colours Palette' but that's not the
same thing..." or, "Well the docs tell me how to change 'Window Behavior',
but how do I work with the program's 'Window Behaviour' function?" You get
So, what would you do? Document the menus and functions as they actually
appear on the screen - with UK spellings? Or use US spellings?
Disregard the option of rewriting the application code to use American
sbrowne -at- unicomp -dot- net
"Writing is like Prostitution. First you do it for
the love of it, then you do it for a few friends,
and finally, you do it for the money." -Moliere