Fwd: NEWS: MSTP makes the switch: email and website nowhyphenless

Subject: Fwd: NEWS: MSTP makes the switch: email and website nowhyphenless
From: punit shrivastava <punitshrivastava -at- gmail -dot- com>
To: techwr-l List <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 29 Apr 2010 17:20:56 +0530

Hi Guys,
How true can it be!! Got it from a friend, so thought of sharing with you


>From the mailing list for the Information Design & Architecture SIG of the

This just came in from a source at Microsoft...


It has been Microsoft style to hyphenate *e-mail* and write *Web site* as
two words, capitalizing *Web*. Today we’re announcing a new direction in
guidance for these words. Updated topics will be published in the internal
June update to MSTP <http://mstp/>.

*email* (noun)

- No hyphen. Current MSTP guidance about using this word as a noun
but not as a verb still applies.


- Lowercase except when referring to a UI element or feature name,
such as *Web Slice,* or in the phrase *World Wide Web*.

- Microsoft Style: the web, web address, web browser, web form, web


- Write *website* and *webpage* as one word; all other two-word web
terms remain as two words.

*Why is MSTP changing guidance on these words?*

We’re making this change to Microsoft style to improve consistency across
Microsoft content and to align with the evolution of these terms in
technological and general usage.

*When should I make the switch?*

Teams will set their own timelines about when to implement these changes in
content. Some teams have already switched; others will plan the switch to
align with a particular product release or publication milestone. Check your
product or team style guide, if you use one.

*Is MSTP moving toward dropping hyphens in general?*

No. Dropping the hyphen from *email* is a style decision particular to this
word. Other e-words, such as *e-commerce,* will keep their hyphens, and all
other words with hyphens will continue to be hyphenated. However, avoid
e-words when you can use words without the prefix, and don’t coin new
e-words. For example, use *commerce* and *mail* rather than *e-commerce* and
*email* when the context is clear.

*What about translation memories?*

Teams that work with localization and translation memories (TMs) may choose
to postpone making these changes until budget is available to update
translations. Please note that because this change in guidance affects
common words, the impact to localization and recycling efforts that utilize
translation memories is likely to be significant. MSTP guidance is intended
to *guide* language choices in Microsoft content and to provide customers
with a consistent, high-quality experience; these are *not* mandatory rules.

*The Microsoft Editorial Style Board*

Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com

- Use this space to communicate with TECHWR-L readers -
- Contact admin -at- techwr-l -dot- com for more information -

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -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/archive%40web.techwr-l.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.

Please move off-topic discussions to the Chat list, at:


Previous by Author: Re: Requirements management systems
Next by Author: Re: Beta documentation quality
Previous by Thread: Font size and line length preference?
Next by Thread: RE: NEWS: MSTP makes the switch: email and website nowhyphenless

What this post helpful? Share it with friends and colleagues:

Sponsored Ads