Help translating my packages into other languages?

Permalink
So Cali from the concrete5.fr team has been really cool this past couple of weeks in helping me translate most of my packages over to French. I'm trying to include these languages files within each packages so that they just work instantly after installation. I'm wondering if there are some other people out there that might be willing to help me do the same for some other languages, particularly German, Spanish, Japanese, and Dutch?

As a thank you I'll grant anyone a free license for each package that they're the first to translate in that language. You can find descriptions of each package here:http://inneroptics.net/concrete5/... ...demos of some of them are available here:http://demo.inneroptics.net/

A bunch of .PO files are attached.

11 Attachments

Tony
 
jordanlev replied on at Permalink Reply
jordanlev
Hey Tony,
I got a request from someone to enable translation on one of my marketplace blocks. But I don't know how exactly to do this. I know I should replace strings in the output with the t() function, but this person specifically asked me to provide .po files -- would you mind explaining to me what it is I need to do to get this set up properly?

Thanks!

-Jordan
Tony replied on at Permalink Reply
Tony
hey Jordan,

it took me a little while to figure out how to do this with packages, the documentation seems a little bit sparse on the subject at the moment, but it's really easy once you know the steps. Here's the approach I use:

1) Download PoEdit:http://www.poedit.net/

2) there's lots of tutorials on the web on how to use PoEdit, so I won't go into details on that here. But in short, you want to create a "New Catalog", fill out the Project Info, enter the path to your package as the Base Path, and add "t" as one of the keywords. After you click "ok" it'll create the .po for you. If it worked for you it'll show a list of a bunch of phrases to translate.

3) Translating is just a matter of filling out the equivalent for each phrase. When you save, it will automatically create a .mo file in the same location.

4) So after someone translates the .po for you, they'll send you back a .po and a .mo file. If you want to add those to your packages, build out this folder structure within your package for each language (in this case french):
/packages/my_package/languages/fr_FR/LC_MESSAGES/messages.mo

I put the .po file there too, so it's easy for people to add to the translations later on:
/packages/my_package/languages/fr_FR/LC_MESSAGES/messages.po


I would be nice if the .po creation was automated through the marketplace upload/repackaging process, since it looks like it can be done with just one command line statement (provided the correct libraries are installed). would probably save developers and international c5 users a lot of time/effort.

best of luck.

-Tony
cali replied on at Permalink Reply
cali