Translation Instructions


So you’re planning on translating Frogatto & Friends? Great!
Although complete, Frogatto is still under development, so its textual content will continue to evolve as we release new versions. But that doesn’t mean, at all, that your help with translation at any given time will not be appreciated.

These instructions are, with minor changes, the response I gave to pawiecki on this thread:

Create a transifex account if you haven’t already, and request for the creation of a translation team for your language.
After the translation team is approved, there are two ways for you to actually start translating:
a) Install a translation catalog editor like poedit: and choose the “Download for translation” option from your language page. When you are done editing, just upload the file from that same page.
b) You may also work online on transifex itself, with the “Translate Now” option; then it’s just a matter of saving your progress there.

While translating, there’s some things you have to be aware of:

  1. Make sure we already have the font characters your language needs, and if they’re to your liking - since we use a custom bitmap font, we’ve been drawing the characters and diacritics as we need them, so some may be missing/off for your language. You’ll be able to find the fontsheets in the images/gui folder.
  2. Some messages have format strings, like this one:

The price is ${final_price} coins. In these cases, leave the content of the curly brackets intact, while positioning it in the way that best fits the grammar of your language.
3. The Frogatto engine won’t automatically break the lines in the messages; you have to do that manually by inputting the newline escape sequence (\n) where appropriate. Not doing this would cause the text to exceed the width of the dialogue box, making parts of it unreadable. As a rule of thumb, the dialogue lines should be about 50 characters wide at most, including spaces; a couple of characters over that may still fit.
There’s a script in the utils folder that may be helpful, as it shows you what messages are over a specific width limit. After opening and saving the file in Poedit, which makes the formatting more consistent, run it from frogatto’s module folder (frogatto/modules/frogatto) as such:

python utils/ po/<lang>.po Where is the gettext locale code of your language.
(Or you can ask me to run the script for you, no problem)

Testing the translation for yourself involves saving the file in the translation catalogs folder (po/.po) and compiling the catalog by running

make update-mo in the top-level folder; you must have gettext utilities installed for that, though, so you can just ask me if you need a file compiled, after you have it uploaded to transifex.


And since the resource file keep changing, don’t forget to watch for it, there’s a feature in Transifex that allows you to get notification every time the resource file is changing. Just click the language you’re working on then click the “watch it button” at the top-right corner.


When this feature got activated you’ll receive an email everytime the resource file is changing.


Here’s a tool for offline translation that you can use as an alternative to Poedit. It creates a translation memory as well.

You can also use Virtaal or Poedit to generate the .mo file which you then stick in [tt]modules\frogatto\locale<language ISO-code>\LC_MESSAGES[/tt]. The full path on Windows is [tt]C:\Program Files (x86)\Frogatto\modules\frogatto\locale<language ISO-code>\LC_MESSAGES[/tt]


From the blog post in November, it seems like you’re getting closers to a release?

This means that I’d need access to the files for translation sooner rather than later, plus a build to test them on. Even if you don’t have 100% string freeze yet, translating the dialogues does take time. So, I’d rather have a head start and fix a few fuzzy strings later than having to rush things.


@GunChleoc good reminder; we’ll look into that sometime soon.