Difference between revisions of "WikiTranslation"
From Synfig Studio :: Documentation
(one statement is excessive - it's hard to create new pages because of it) |
m (Language codes list ISO 639-1 link) |
||
| Line 19: | Line 19: | ||
== Useful Links == | == Useful Links == | ||
| − | * | + | * http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes |
== Possible Solutions == | == Possible Solutions == | ||
Revision as of 17:24, 31 January 2008
Contents
For Translators
Page with a translation must bear the name of original English page, plus languages abbreviation (two-letter language code) preceded by a '.', e.g. for About, page in Russian will be About.ru.
Advantages:
- Titles are in one language, which is good for referencing and keeping wiki documentation in order.
- It also provides a clear mapping between original and translated pages.
- It is easy to implement.
What functionality I expect from Multilanguage Extension
- All pages named as described above.
- There must be a list of available translations for current page on top of each page. Let's call it "Page languages list". (Extension detects if page with each language code exists).
- There is a field in the user preferences, called "Language" (Already exists in MediaWiki)
- Navigation improvements:
- Let's say user have Language field in preferences set to 'tr'. Then:
- if user requests page Main Page, and page Main Page.tr exists, he automatically redirected to Main Page.tr.
- if user clicks some other language in "Page languages list", then his "Language" field in preferences sets to that language, and he continues browsing, according to previous rules.
- Let's say user have Language field in preferences set to 'tr'. Then:
- It would be nice to have Language field set up according the browser settings automatically for new users and guests.
