Translating:Old-How to start/en
| Next step | What can be translated |
|---|
- How to start
Follow these steps to translate on translatewiki.net:
- register or log in to translatewiki.net
- remember that this will be the name which will be added to the MediaWiki software files ("@author YourUsername")
- create a user page with some information and links (what language you are going to translate, ...)
- set your user interface to the language you will be working on
- find out if your language has already some maintainers on the language status page
- if your language has maintainers, contact them and ask how you can help
- if not, you can take over maintenance of your language. Read the documentation and add details to the status page
- If you are translating MediaWiki and there are translations in another wiki, you may want to ask for the messages of your project to be imported. You can request this on the Tasks page.
- ask for translator privileges
- if your knowledge of English isn't that good, you can request for language(s) to be added above the edit form to help you (example)
- start translating at Special:Translate
Offline translation
In Special:Translate you can export a message group to a gettext .po file, and work on that offline. Make sure you save the .po file as UTF-8! Return it to "translatewiki AT translatewiki DOT net" and make sure to note what your translatewiki.net username is – all changes will be attributed to it. More is explained on Translating:Offline.
Recommended process for translating MediaWiki
Make sure you have set your language preference to the language you will be working on. Translators of other projects can ignore this list.
- first translate the most often used messages
- complete the core messages
- check if you should translate any optional messages
- do a consistency check (terminology, formal/informal) on your localisation
- translate special page names, magic words and namespaces on Special:Magic
- translate the extension messages used in Wikimedia wikis
- translate the remaining extension messages
- do a consistency check (terminology, formal/informal) on your localisation between core messages and extension messages
- start maintaining your language's localisation on a regular basis. At least once per month is recommended.
Read on if you want to know more. Reading on is not required, although advised for a proper understanding of more advanced localisation features. You could spend a few days translating, though, and come back when you think you need more information.
Remember: translate links, namespaces, and messages as they are and do not deviate from the source message more than needed!