Revision as of 10:23, 26 July 2011 by hamishwillee (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Help:Language Policy

From Nokia Developer Wiki
Jump to: navigation, search

This Help topic explains the Nokia Developer Wiki Language Policy. Specific information on translating articles is available here.



The primary and default language of Nokia Developer Wiki is English, however we encourage users to translate articles, and to create original articles in other natural languages including Chinese, Japanese, Portuguese, Russian and Arabic (to name a few!). Entry points to the main languages are provided through the Natural Languages section of the sidebar.

In order to ensure that the wiki remains usable, this language policy defines how non English articles are named and categorised and organised.

Article Categories and the Language code

Every article in a non-English language must contain at least the category code for that language. The main categories are:

The article should also have any other relevant English categories (for example Symbian C++, Messaging etc.), as discussed in Help:Categories. Note, do not create or use "non-English" categories.


  • English articles do not required a language code as this is the default language (an article without a language code is assumed to be English)
  • The wiki has several hundred English categories. If a natural language variant is required for every one, categories quickly become unmanageable.


A portal can be thought of as manually created "category" page. We use portals to display articles for a category in just one particular language. For example the portal Portal:Symbian C++ (Português) displays all topics that have categories both Lang-Portuguese AND Symbian C++.

Note.pngNote: Using portals means that we don't need to use categories in non-English languages. This in turn means that users need to make fewer decisions when categorising articles

Portals are very easy to create using the {{LanguageCategoryPageProxy}} template. This inserts all the dynamic lists you'd normally see on a normal category page, filtered by language. You can of course add other descriptive text for the category/portal above the template. The example below shows how we created the "standard infrastructure" for the Portuguese Symbian C++ portal.

{{LanguageCategoryPageProxy|language=Lang-Portuguese|Symbian C++}}

By convention we name portal articles with the prefix "Portal:". You should use a natural language translation of the category name for the rest of the description and text to indicate the language if this is not obvious.

Tip.pngTip: Portal pages for a natural language should include its language code category

Usually there isn't time to create a portal for every possible category vs. language combination. A more usual approach is to create portals for the most important categories, and then manually create a Portal:Other Categories topic to group all other categories. So for example Portal:Outras Categorias list all Portuguese articles that aren't in any of the other main portal pages.

Article Names

As a general rule, non-English articles should be named using their natural language. There are two exceptions:

  • "Proper names" should not be translated, and are by default reserved for English topics. When creating the topic for another language, this should be differentiated by appending the language after the topic name. For example:
    • If "Symbian Web Runtime" is the English topic, then a topic in the same subject in Portuguese would be: Symbian Web Runtime (Português). Similarly we might have articles like "Symbian Signed (中文)", "Ovi Browers (日本語)", "Symbian C++ (Русский)".
    • An article title "Flash Lite" should not be used for a non-English topic
  • Where an article is a portal the initial text should be "Portal:". The remainder of the name should be in the natural language, unless its a "proper name".
    • For example, "Portal:Symbian Web Runtime (Português)"

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.