New guides to translating your project
I’ve revamped our guides to translating your project in Launchpad, with help from Jeroen and Danilo. You can find them here:
https://help.launchpad.net/Translations/YourProject
Let me know if you think there’s anything missing or that could be better explained.
August 27th, 2009 at 10:29 pm
Thanks for this guide! One thing that would be nice to cover, and that I am currently stuck on, is what to do with the .po files that you get from using the auto-export. Previously I would manually export mo files, but now that I’m automatically exporting to a branch, I’m not sure how to compile those to mo files, and I have had a surprising amount of trouble finding the solution online. So, I can’t figure out how to actually use them in my application from the branch.
Also, for people new to translating a project, I didn’t see anything covering the general i18n process such as using gettext or generating the template; the guide seems to assume you already have enough knowledge to have a template, but don’t know how to do anything else, which might cut out a bunch of potential users of this guide.
August 27th, 2009 at 11:04 pm
Michael: $ msgfmt -cv file.po
September 5th, 2009 at 4:56 pm
Ping! Any response to my questions and comments?
September 15th, 2009 at 2:16 pm
Michael: Kamíl already answered your question about how to convert PO files to MO files. We also have a bug open on allowing a choice of export formats, though I don’t know whether or when we’ll get to that since it’s not hard to produce MO files yourself.
For documentation about gettext, the formats, tools etc. look for the link in this part of the document:
“You can find out more about these file formats and using GNU gettext in the .”
For more good practice and information about the general i18n process, try the link in the “Quick tip” bar.
Jeroen
September 15th, 2009 at 2:18 pm
Ah, it looks like my angled brackets got turned into markup. Look for “…and using GNU gettext in the GetText manual.”
September 16th, 2009 at 11:01 pm
Thanks Jeroen. Kamil’s comment was definitely not on the page when I commented, and it just showed up in Google Reader the other day so something weird must have happened with it. Either way, thanks for the responses!