Welcome to AnswerHub Answers!
Not only can you experience AnswerHub firsthand, but you can also ask and explore questions and answers about AnswerHub.
To get started, try typing a question in the search bar. If your question hasn't been asked, try posting a new question.
If you are a current customer, please use the Customer Success portal instead of this communtiy.
If you're coming from meta.osqa.net, please visit the OSQA space for all your old content. If you can't login, please request a temporary login to gain access to your account.
What is a workable recipe to work on translations?
I started translating OSQA for French, and experimented my work with `./
manage.py compilemessages`. I worked fine, but after a hundred lines, I noticed some words and lines, although translated in the po and compiled, were still appearing in English. After some search, I discovered the po files actually in the SVN repository were not generated with the latest source code. Therefore, I ran `./
manage.py makemessages` to update the po files that would actually match the source code. I discovered that it created a complete mess in my po file. Some of the translated lines do not correspond anymore to the English line. I am feeling very disappointed, just like I lost a couple of hours for nothing. Is there any recipe to avoid such annoyance? I got a version of my po file before regenerating th po. Do you feel like adding it to the repository (only 100 line translated)?
Hi Didier, I ran into similar problems when I started translating OSQA into German. I think I worked out a translation recipe that Works For Me. If you find out about better ways to do it, please share! ### Requirements ### - [SVN Checkout of OSQA][1] - [Babel][2], a Python-centric translation software - [BabelDjango][3], Django plugin for the above - [PoEdit][4], a graphical, multi-platform translation file editor (killer features: *automatic translation* and *update from POT file*) ### Setup ### (See [here][5] and [here][6]) 1. Create a directory (*not* under the SVN checkout) to put your translation file and Babel settings into (`mylocale`, say). 2. Copy this into a file called `babel.cfg` in your `mylocale` folder:
`[python: **.py] [django: **/templates/**.*]`3. Make sure you are in the `mylocale` directory, then create the translation template `django.pot` by running
`pybabel extract -F babel.cfg -o django.pot` *`path-of-your-svn-checkout`*4. Start PoEdit and create a new catalog from the template (`File > New catalog from POT file...`). 5. Fill in the catalog details under the `Project info` tab. `Language` is necessary, `Country` should probably be left empty. There is no need to fill in anything under `Paths` or `Keywords`. Save the file as `django-`*`languagecode`*`.po`, e.g. `django-de.po`. 6. Check out the PoEdit Help (`Help > Contents... > Translation Memory`) for instructions to set up the automatic translation. ### But what if there's an update? ### No prob: - Your own translation is not in the SVN tree, and will therefore not be overwritten when you `svn up`. - Simply recreate the `django.pot` file (Step 3 above), then update your `.po` file using PoEdit: `Catalog > Update from POT file...` ### Tips ### Use a version control system for your translation files. That way, even if you accidentally overwrite it, you can just revert to your old version and be happy. [1]: http://wiki.osqa.net/display/docs/Downloading+OSQA#DownloadingOSQA-HowtoDownloadusingSVN [2]: http://babel.edgewall.org/ [3]: http://babel.edgewall.org/wiki/BabelDjango [4]: http://www.poedit.net/ [5]: http://www.gabsoftware.com/tips/a-guide-for-wordpress-plugins-translators-gettext-poedit-locale/ [6]: http://babel.edgewall.org/wiki/BabelDjango
Regarding recipes, Google Translator Toolkit just added support for PO files. You upload eg the OSQA English PO file and it can give you a head start on your translation. I just tried it for a Swedish translation and it works quite well. It didn't translate the fuzzy messages and I wanted those as well so I just removed the fuzzy markers first. There were also some minor issues with the formatting of the new PO file but maybe we can gather workarounds for those in comments to this thread. Most issues were related to Python and HTML formatting and some may also be reported and fixed by Google.
