Always use latest Git version of the po file to translate. You can optionally
- translate online at our translation
- server where you can also get the latest po files and merge them
- with your translations. For creating a new translation simply use
- po/phpmyadmin.pot and generate
- po/LANG_CODE.po for your language (you can use
- msginit -i po/phpmyadmin.pot -l LANG_CODE --no-translator -o po/LANG_CODE.po
- to do this) or ask on the mailing list to add the translation to the web
- interface. More details are available on our wiki.
-
- Please note that we try not to use HTML entities like é in - the translations, since we define the right character set in the file. - With HTML entities, the text on JavaScript messages would not - display correctly. - However there are some entities that need to be there: quotes, - non-breakable spaces, ampersands, less than, greater than. -
-- You can then put your translations, as a zip file to avoid losing special - characters, on the sourceforge.net translation tracker. -
-- It would be a good idea to subscribe to the phpmyadmin-translators mailing - list, because this is where we ask for translations of new messages. -
- -
- Documentation is being translated using po4a and gettext (see
- documentation
- for existing translations). To start, checkout
- localized_docs/po
- from Git, or just go to the translation server
- and translate it online. If your language is missing, just contact
- Michal Čihař; he will add it. If
- you prefer to directly translate the po files, please put updated ones into our
- translation tracker.
-
Translations are very welcome and all you need to have are the language skills. + The easiest way is to use our online + translation service. + You can check out all the possibilities to translate in the + translate section on our website. +