Table of Contents See AlsoOther Languages
Articles with non-English words in the title and/or body text should include the language code from the list below in parentheses as the last seven characters of the title, like this: "Wiki
Article Title (pt-BR)". Not only is this important so that the reader quickly knows what language the article is in when searching, but it also is necessary to
avoid a bug where the non-English article "steals" the ability to have an English article with a similar name.
NOTE: Please do not include "(en-US)" in the title of English articles. See
Wiki Governance: Whether or Not "(en-US)" Should be Added to the Title of English Articles.
Also, you need to include the code as a tag at the bottom of the article. For example, a tag for a Brazilian Portuguese article would be "pt-BR". This is so that we can click the tag and see all the articles in that language (click the links
below to see). Because readers can filter by multiple tags, this allows them to see only the articles in a tag list that are in a specific language and on a specific topic. Not only is this practice convenient for the people who read that language, but it's
also necessary for when we migrate the files to a language-specific Wiki version.
Some of the codes below are linked to the tag pages that list out all the articles that use that tag (in other words, click the language code to see all the articles in that language):
This is useful.
What about the translation method: manual or automatic (by means of Microsoft Translator)?
Are contributors encouraged to write articles both in English and in their native languages (or in any other language they are able to speak/write)? If this is the case, shall they have to create a page (like the one at social.technet.microsoft.com/.../microsoft-sql-server-2008-r2-sp1-release-notes-language-options.aspx) that provides links to the multiple translations of a page?
Thanks for your comment Luigi.
For links: we're exploring various options, and for now, putting the links to other languages in the article itself is a popular option (like on this page - social.technet.microsoft.com/.../706.aspx ).
For translation: this is very much encouraged. At this point, I'm suggesting staying away from "pure" machine translation as this is still a lot of copy/paste work and a human's time might be better spend doing things that humans are good at. But using automatic translation AND post-edit it can save a lot of time.
I've sent you a private message to discuss options including creating an article with relevant info so all can benefit...
Thanks Bruno. I'll answer your message as soon as possibile.
Nice differentiator and addition
Ed Price - MSFT edited Revision 43. Comment: Adding Georgian link. First article is up!
Ed Price - MSFT edited Revision 44. Comment: Added the note about the English titles, to increase awareness.
yottun8 edited Revision 45. Comment: Added "ar-SA" link.