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:Re: English variant in Telecom materials From:"Moshe Kruger (AllWrite)" <moshe -dot- kruger -at- gmail -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Mon, 30 Jul 2007 10:57:00 +0200
My question was based on two premises:
1. English taught and spoken in the countries/areas I enumerated is
distinctly British.
2. I canot remember where, but somewhere I learned that European telecom
materials are written in British English.
So, it would seem clear how I should proceed. Only, I have a niggling
thought that the US brand has become so dominant, perhaps I should give in.
In other words, "if you can't beat 'em join 'em".
On 7/30/07, Caroline Tabach <caroline -dot- tabach -at- gmail -dot- com> wrote:
>
> While many high-tec companies do indeed make an effort to write their
> material in American English, it seems a far fetched demand to expect
> that American-English can be a dialect written specifically for (by
> someone outside the US producing a set of user guides for a worldwide
> audience). This sounds to me like the 2 versions of Harry Potter, one
> in British English and one in American English; except that they are
> intended for children, not adults (and I can understand wanting to
> make the language in the books more familiar for children to read,
> even though I do not agree with this policy).
> I do not think that there are many companies who actually localize
> their variants of English and publish a user guide for Europe and the
> UK, and a different version for the US.
>
> (unless some of you out there do make such "translations")
>
> On 7/30/07, Lauren <lt34 -at- csus -dot- edu> wrote:
> > I would proofread British-English documents in my head that were written
> for
> > *me* as the audience. I would read and interpret the document as though
> it
> > were written in American-English and make appropriate translations from
> > British to American. If I, as an American, am the audience, then the
> > document should be written for me in American-English.
> >
> > When I read British documents that are understandably British, then I
> don't
> > get annoyed because the audience of those documents is not specifically
> > American. It is rather insulting for a writer to write a document for a
> > specific audience, like an American audience, and then write that
> document
> > in a dialect or style that is not the style that the audience
> expects. So,
> > it's annoying.
> >
> > The second part of your comment about a non-American reader being
> annoyed by
> > a document written for an American audience is irrelevant. Writing for
> the
> > audience is important and avoidance of insulting or annoying the
> audience by
> > writing in the dialect of the audience is a part of writing for the
> > audience.
> >
> > This of course does not by any stretch mean that British-English is
> > annoying, but a document written specifically for an American audience
> in
> > British-English would be annoying, just like a document written
> specifically
> > for British audience in American-English would be annoying.
> >
> > If it is true that technology documents are written in American-English
> as a
> > de facto standard as Moshe Kruger states, then it should really be the
> case
> > that the audience of those documents does accept that the documents are
> > written in American-English, otherwise the documentation could be
> annoying.
> >
> > Lauren
> >
> >
> > > -----Original Message-----
> > > From: techwr-l-bounces+lt34=csus -dot- edu -at- lists -dot- techwr-l -dot- com
> > > [mailto:techwr-l-bounces+lt34=csus -dot- edu -at- lists -dot- techwr-l -dot- com] On
> > > Behalf Of Stuart Burnfield
> > > Sent: Sunday, July 29, 2007 8:05 PM
> > > To: techwr-l -at- lists -dot- techwr-l -dot- com
> > > Subject: RE: English variant in Telecom materials
> > >
> > > Why would you be annoyed? If the documents are written in British
> > > English, then British spelling and usage would be correct in that
> > > context, so what you're doing isn't proofreading.
> > >
> > > What if one of your non-American readers sent feedback saying
> > > she'd just
> > > proofread your manual, was very annoyed, had highlighted all the US
> > > spellings, refused to finish reading it, and so on?
> > >
> > > Stuart
> > >
> > > Lauren said:
> > > > I would have a hard time dealing with instructions written in
> > > > British-English because the support documents that I read are
> > > > normally American-English. Not that I wouldn't be able to read
> > > > the documents, but I would get very annoyed and proofread the
> > > > document in my head while I read, so I might get too annoyed
> > > > and never finish the document,
> > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > >
> > >
> --
> Caroline Tabach
> Technical Writer
> e-mail: caroline -dot- tabach -at- gmail -dot- com
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Create HTML or Microsoft Word content and convert to Help file formats or
> printed documentation. Features include support for Windows Vista & 2007
> Microsoft Office, team authoring, plus more.
>http://www.DocToHelp.com/TechwrlList
>
> True single source, conditional content, PDF export, modular help.
> Help & Manual is the most powerful authoring tool for technical
> documentation. Boost your productivity! http://www.helpandmanual.com
>
> ---
> You are currently subscribed to TECHWR-L as moshe -dot- kruger -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
>http://lists.techwr-l.com/mailman/options/techwr-l/moshe.kruger%40gmail.com
>
>
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
>
>
--
Moshe Kruger
AllWrite Information Design
Mobile: +972-54-24-64-774
-----------------------------------------------
APIs/SDKs * Doxygen consultation *
User manuals * White papers *
Marketing collateral * Translations *
Training courseware * GUI design
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-