Difference between revisions of "WikiTranslation"
From Synfig Studio :: Documentation
(Wiki translation scheme proposal) |
(OUTDATED INSTRUCTIONS MESSAGE) |
||
| (18 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | THE FOLLOWING ISNTRUCTIONS ARE OUTDATED. WIKI TRANSLATION USES DLP MACROS NOW. PLEASE DO NOT USE THIS INSTRUCTIONS | |
| − | + | {{TranslationBar|CONTENT={{Tr/en}} · {{Tr/de}} · {{Tr/es}} · {{Tr/fr}}}} | |
| − | + | == 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. | * 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 also provides a clear mapping between original and translated pages. | ||
* It is easy to implement. | * It is easy to implement. | ||
| − | + | When translating pages do '''''NOT''''' move them. Simply copy the content and add it to a new page. | |
| − | + | === The Translation Bar === | |
| − | + | ||
| − | + | ||
| − | + | The bar containing all available languages that is shown on top of the page is a {{l|Template:TranslationBar|template}} that you should use on all of your translated pages. The translation bar template is language-dependant so if there is no translation bar template for your language you should translate the template first. :) | |
| − | + | Please sort the languages in the translation bar by the 2-character language code (but always list English first!), and don’t forget to update all other translations of the page you’re currently working on! | |
| − | + | ==== Language Templates ==== | |
| − | < | + | To ease the input of languages that your keyboard is unable to reproduce, a couple of templates have been created. The name of those templates is constructed by appending the language code (e.g., “en” or “zh”) to the string “Tr/”. The template for the French language is “<tt>Tr/fr</tt>” and will output “<tt><nowiki>{{l|</nowiki>''current page name''.fr|Français}}</tt>” to create a link to the French version of this page. |
| − | + | ||
| − | </ | + | |
| − | + | As templates can be nested this makes creating a large translation bar pretty simple: | |
| − | < | + | <tt><nowiki>{{</nowiki>TranslationBar|CONTENT=<nowiki>{{</nowiki>Tr/en}} · <nowiki>{{</nowiki>Tr/de}} · <nowiki>{{</nowiki>Tr/fr}} · <nowiki>{{</nowiki>Tr/pl}} · <nowiki>{{</nowiki>Tr/pt}} · <nowiki>{{</nowiki>Tr/ru}} · <nowiki>{{</nowiki>Tr/tr}} · <nowiki>{{</nowiki>Tr/zh}}}}</tt> |
| − | < | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | }} | + | |
| − | + | ||
| − | }} | + | |
| − | + | ||
| − | }} | + | |
| − | + | ||
| − | }} | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | } | + | |
| − | + | ||
| − | + | ||
| − | </ | + | |
| − | + | Unfortunately this does currently not work with templates for other languages than English. | |
| − | + | ||
| − | + | === To translate the text in images === | |
| − | + | ||
| − | + | ||
| − | + | In {{l|Releases/Artwork}}this page you will find all the artwork (including editables files) of all the artwork me make for every new release of the project. | |
| − | + | {{l|Styleguidelines|Here}} you can read our graphic style guidelines, where you will find help on how to create and edit the images of this site. | |
| − | + | == 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 {{l|Special:Preferences|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 {{l|Main Page}}, and page {{l|Main Page.tr}} exists, he automatically redirected to {{l|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. | ||
| + | * It would be nice to have Language field set up according the browser settings automatically for new users and guests. | ||
| − | == | + | == Useful Links == |
| + | * http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes | ||
| + | |||
| + | == Possible Solutions == | ||
* http://www.mediawiki.org/wiki/Extension:MultiLanguageManager | * http://www.mediawiki.org/wiki/Extension:MultiLanguageManager | ||
| − | |||
| − | |||
| − | |||
* http://www.art122-5.net/index.php/MediaWiki_Multi-language | * http://www.art122-5.net/index.php/MediaWiki_Multi-language | ||
| + | * http://www.mediawiki.org/wiki/Category:Internationalization_extensions | ||
Latest revision as of 13:28, 5 March 2010
THE FOLLOWING ISNTRUCTIONS ARE OUTDATED. WIKI TRANSLATION USES DLP MACROS NOW. PLEASE DO NOT USE THIS INSTRUCTIONS
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.
When translating pages do NOT move them. Simply copy the content and add it to a new page.
The Translation Bar
The bar containing all available languages that is shown on top of the page is a template that you should use on all of your translated pages. The translation bar template is language-dependant so if there is no translation bar template for your language you should translate the template first. :)
Please sort the languages in the translation bar by the 2-character language code (but always list English first!), and don’t forget to update all other translations of the page you’re currently working on!
Language Templates
To ease the input of languages that your keyboard is unable to reproduce, a couple of templates have been created. The name of those templates is constructed by appending the language code (e.g., “en” or “zh”) to the string “Tr/”. The template for the French language is “Tr/fr” and will output “{{l|current page name.fr|Français}}” to create a link to the French version of this page.
As templates can be nested this makes creating a large translation bar pretty simple:
{{TranslationBar|CONTENT={{Tr/en}} · {{Tr/de}} · {{Tr/fr}} · {{Tr/pl}} · {{Tr/pt}} · {{Tr/ru}} · {{Tr/tr}} · {{Tr/zh}}}}
Unfortunately this does currently not work with templates for other languages than English.
To translate the text in images
In Releases/Artworkthis page you will find all the artwork (including editables files) of all the artwork me make for every new release of the project.
Here you can read our graphic style guidelines, where you will find help on how to create and edit the images of this site.
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 Synfig Wiki, 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.
