problems with translation and information collector

Tuesday 04 April 2006 3:09:42 am

Hi,
has anybody experience in translating classes with information collection in a multilangual site?

All the attributes I have in a class that collect information are not really translatable, even if I mark them as translable (seems to translate the collected info). The website displays always the Name of this attribute.

Every comment and hint is welcome :)
Heiner

Thursday 28 September 2006 2:58:55 am

This problem still exists, its a pitty, but it doesnt work. I tried this to translate the names of the information collectors:

{$ContentObjectAttribute:item.contentclass_attribute.name|i18n( 'myarea/texts' )}

no luck, very strange. Does anybody translated an information collector ?

Thursday 28 September 2006 12:29:09 pm

Hello Heiner

ezlupdate cannot determine all possible values of the variable you set as input for i18n here. But the translation should work if you manually insert all possible values of the variable (meaning the names of all your attributes) into the translation.ts yourself.

So if the name is 'foo' which you want to translate to 'bar', add the respective info to your translation.ts in the context you have specified. As the translation.ts is an xml file you can open it in any txt editor (be careful to keep the utf8 encoding if necessary). You can see that the structure is quite easy to understand.

Please note that the ezlupdate will choke on variables as input for i18n so you might have to comment out the respective template line, run ezlupdate and then comment the line in again.
Afterwards add the additional translations as required.

Greetings from Luxembourg

Claudia