There are four different areas that are involved when translating phpList:
How does this work:
Everyone can add suggestions on the translation site. Only selected administrators are allowed to approve the translations. If you are interested to become a moderator for your language, let the team know on the Translators Mailinglist 2)
In order to help out translating, you need to do the following:
If you want to get familiar with the Pootle system, try the Foobarian language, which is there for testing. You can play around with it, whatever you want.
The translation system has two modes for translations. One is to
Suggest translations and the other one is to
Submit translations. Anyone (even when not logged in) can send suggestions, but only approved accounts can submit the translations.
Once you have made a few changes in the translations, you can go to the phpList Dev system and choose “Update translations” from the menu, under “System” to see the changes.
You can also try to run phpList on your local system
There are a few things that you need to know when you start or edit a translation
It is essential that the translation has the same codes in it. Otherwise the text will disappear completely. So, for example
Processed %d out of %d messages
needs to have at least two times %d in your translation.
pagetitle:. For example
You do not need to translate the “pagetitle:” bit, just the text after it. So, the example would be “Database check” as a translation.
Note: pootle only shows the msgid which is pagetitle:dbcheck. Please look for the original english string in adlin/locale/en/phplist.po which would give you “Verify the DB structure”, and translate that string
You do not need to translate the “pagetitlehover:” bit, just the text after it. So, the example would be “Verify that the database structure is correct” as a possible translation.
Note: pootle only shows the msgid which is pagetitle:dbcheck. Please look for the original english string in adlin/locale/en/phplist.po which would give you “Verify that the current database structure is correct for the current version of the code”, and translate that string.
user -> Subscriber message -> Campaign email -> Either "email address" or "email message" (depends on the context)
and there may be similar words that require a clear definition. It is up to the language managers to determine this per language. Language specific rules for the translation are collected in the Notes on Translations.
to be added
To translate the documentation, register for this Wiki and request to be made a moderator for your language. You can then go ahead and create translations.
Notes on Translations Language specific rules for the translation