In the last few years, Magnolia's code base has grown tremendously. Many modules have been added since the community last had a chance to contribute translations. As a consequence, a lot of the new modules are only available with an English user interface, and existing modules have outdated or incomplete translations. See currently supported languages.
We need your help!
If you want Magnolia in your own language, now is your chance!
We're convinced that you, being a Magnolia user, can do a better job translating Magnolia than a professional translator who doesn't know Magnolia. So we decided to give it a try and open up the translation process to anybody in the Magnolia community who wishes to improve the Magnolia user experience. All contributions are welcome; don't be afraid by the humongous task ahead of you, your help is appreciated no matter how many (or few) items you translate!
If you're interested in helping translating Magnolia and its numerous modules, we can promise fame and glory, but we're also throwing in some goodies for the best translators! Watch this space for details, we're currently sorting the details out, so I can't promise anything yet
Please get in touch, either with me directly, or via the mailing list; we'll need to know which language you'd like to translate to, and your Google ID. (see below) Further communication and effort synchronization will happen through the mailing list, so subscribe now if you're not already on there. (if this creates a lot of traffic, we might branch out to a specialized list)
If you have already translated parts of Magnolia (for your projects, perhaps?), we would also like to hear from you, of course !
With the files to translate being scattered across a lot of modules, we've realized it wasn't really easy to get started, nor to get an overall picture of the work left to do.
We have gathered all translation files for all our modules into spreadsheet documents: one document per language, with one worksheet per module. This way, a translator can focus on his language only, without having to switch between separate documents. To ease the process, we've decided to use Google Spreadsheet, which makes it easy to share and collaboratively work on these documents.
Here's a screenshot of what it looks like, using the French document as an example:
The first column holds the "key" of the text to translate. This is used internally in Magnolia (and dialogs, paragraphs, templates, ...). The second column holds the current English translation, for reference. The third and fourth columns are the ones you'll be working with: the translation of this item in your language, and the status of the translation. The bottom of your screen shows a list of modules; each module's translations for your language is in a different worksheet. The more the better
Once translations are ready to be integrated back into Magnolia, we will transfer these documents back into the original source files using some scripted magic, based on the status of each item: only items with the status "ok" will be transferred back. We currently use the following statuses:
ok: either this item was already translated (in the past, or by someone else), or you just did and validated it. Congrats!
to check: this item needs to be validated: either because our little script found it suspicious that the translated version of a word was the same as its English counterpart (which is sometimes just fine, in which case feel free to set it to "ok"), or because you or someone else deemed this translation poor or incomplete: feel free to improve it !
automated translation: we had no prior translation for this item, so with the help of Google Translate, we're hopefully making your life easier by providing an automated pre-translation. Please improve this translation if needed, and switch the status to "ok" !
Please note that a translation with a status of "ok" might still need to be verified and improved: keep your eyes peeled for outdated translations! (For example, there are unfortunately some Chinese and Portuguese items which have been corrupted in the past due to encoding issues; we've tried to set these back in the "to check" status, but we're not flawless.)
Of course, if you feel more comfortable using other tools, and/or if you already have translated (parts of) Magnolia into any language, we'll welcome your contributions as well!
Tips & tricks
- Context: Often times, you'll probably be wondering what the context of a certain item is.("Where is xxx.yyy used?") Hopefully, in the future, we'll have a better system that can provide such context, or translations inline from within Magnolia, but for now we're stuck with this. In case of doubt, just don't hesitate, and ask the mailing list for help. This will help other translators too.
- HTML entities: There a few places where we've used HTML entities, such as
« Preview, which at runtime will be rendered as
« Preview. Such "special characters" can stay as-is; accented letters or other non-european characters don't need to be encoded with HTML entities. (No need to use
- Lost in translation? Again, do not hesitate to ask for help.