Comments on: CakePHP 1.2 i18n/l10n

By: icko

icko — Wed, 27 Aug 2008 06:50:04 +0000

thx for this article

great thing to help you with your translation files are the gettext tools. for example it can create the .po files for you automatically by extracting all the strings defined in the __() function.

http://www.gnu.org/software/gettext/#TOCdownloading

By: Gustav Ernberg

Gustav Ernberg — Mon, 30 Jun 2008 21:31:35 +0000

Ok, that’s how I’ve done so far, thought perhaps it existed an easier solution

By: admin

admin — Mon, 30 Jun 2008 21:27:03 +0000

I do not know what the character limit is, but I would break the page content into several smaller strings. The largest single string I have ever used is a single paragraph.

By: Gustav Ernberg

Gustav Ernberg — Mon, 30 Jun 2008 21:22:28 +0000

Nice post!
Do you know how to do if I want to make a whole page “translateable”, msgstr’s has a limit at some charachters.

By: zabroc

zabroc — Fri, 11 Apr 2008 08:26:09 +0000

Ok, i’ve got it, but it is a bad hack:

Configure::write(’Config.language’, ‘de’);
$curInst = I18n::getInstance();
$curInst->__l10n->found = false;

By: zabroc

zabroc — Fri, 11 Apr 2008 08:15:35 +0000

I tried it your way but it is not working. There is a language found property ($found ) in l10n you can not change once it is set. (or I haven’t found a way yet

By: admin

admin — Thu, 10 Apr 2008 19:05:57 +0000

I have not tested but presumably German is the default language, and then you could use setLang(”en”), as defined above, before composing the email, and then setLang(”de”) after.

By: zabroc

zabroc — Thu, 10 Apr 2008 17:59:39 +0000

I would like to switch language within a component, like the page is in german but emails which are being sent via email component are in english. How can i switch the language (and switch back afterwards) .

By: admin

admin — Tue, 08 Apr 2008 23:45:43 +0000

Some useful comments from Daniel.S:

… thought I should mention that with __(), it helps to use the full string text, not just a message ID. That way, if people need to create new translations, or you look at it a long time down the track - you won’t be wondering what ‘where_pin’ is actually meant to say.

For example:
__(’Where is my PIN?’)

and in the PO file, it will have

msgid “Where is my PIN?”
msgstr “”

That way, when you create a translation, all you need to do is look at
the POT file and translate away:

msgid “Where is my PIN?”
msgstr “Hvor finner jeg PIN-koden min?”

This is the way i’ve seen it done in Drupal, and it makes sense.

By: cpe

cpe — Sat, 15 Mar 2008 11:08:33 +0000

When writing the default.po file, remember to use double quotes around the text, when defining the msgid.
Single does not work!
It would be nice if both kind of quotes did work!