RegexPlanet Translations

These are the translation strings for RegexPlanet. The scripts used are all in the bin directory.

Notes to translators

I recommend using poedit, a GUI editor with versions for Windows, Mac & Linux. But you can use any text editor that supports UTF-8.

If a MsgId starts with %, then it is a macro. Look in the English translation (en.po) for the text.

If a MsgId ends with .html, then the text can contain HTML, and must be safe to embed in a webpage as-is.

Entries with the fuzzy flag set are from Google Translate. If you fix one (or if by some stroke of luck it is correct), unset it. Once there are no more fuzzy entries, I can change the %html.lang.attribute to the raw language code. This is necessary to comply with Google Translate's terms of service.

New translations

Let me know before you start a new translation (i.e. creating a brand new .po file). I will make a blank .po file with the correct metadata lines at the top.

Workflow

This is the workflow that gets the translations from this project into RegexPlanet:

1. run extract.sh. This creates the original.pot with all the strings that have to be translated, and adds blank entries to all the XX.po files for new strings.
2. run gtrans.sh. This fills in any blank entries in the XX.po files with a machine translation.
3. Human translators edit the XX.po files and update all the fuzzy entries.
4. run process.sh. This transfers the text in the XX.po files back to the website.

Credits

polib - python library to deal with .po file format from David Jean Louis

Google Translate - for machine translation