This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit

eZ Community » Forums » Suggestions » Idea for improvement of i18n...

Idea for improvement of i18n translation system

Idea for improvement of i18n translation system

Friday 19 December 2008 10:48:48 pm - 4 replies

Hi all,

I'm currently building up a new multi-language website and I've to customize both some system messages (es. in login page) and some custom messages.

Now: with the current system I insert a string and mark it with i18n, then I go to .ts file and create the relative voice (equal to my string). Then repeat this operation with all .ts files for each language.

This system sucks for many causes:
1. If I have to modify it later, I must modify the marked string in all .ts files
2. The same message has often to be modified:
- for native languages directly by the editors (in order to improve it)
- for translating strings by the translation agency (often an external agency)

This is very uncomfortable because I have to manage the different versions and modifications on different .ts files, and I send files by email to many people. In addition always the editors (or translation agency) that write the text has not technical skills for use QT or other xml editor.

The result is that many messages remain in technical language (always different from human language provide by an editor happy.gif Emoticon and many translations uncompleted.

What would be a great solution?

Just to move the translation system to admin interface as "ezcontentobject".

I tried to do this by creating a "Translation" class and give it a "text" attribute. In this way I can create several objects, call it directly from code as ezcontentobject and place in tpl without think anything about the translation or message to insert.

On the other side I give to my customers and translation agency, the possibility to modify it simply from admin interface (using the provided translation mechanism for objects) without learn how to handle a .ts file.

We had a great improvement with this system in order to provide more accurate messages in the web site and to make easy the manage messages translation.

I think this is a solution quite better than original system and I hope this idea could be help others eZ users.

At the same time let me invite eZ developers team to provide a build-in mechanism (more sophisticated than a Class) which could be substitute gradually the actual i18n system with the hack described.

Best regards,
Maurizio Betti

Modified on Friday 19 December 2008 10:52:38 pm by Maurizio Betti

Saturday 20 December 2008 8:17:01 am

i would prefer let the ezcontentobject table just for content and not for other things. correct me if i'm wrong, but if you have 12 literals for example in a template, you'll need 12 fetch("content", "object"blunk.gif Emoticon calls for getting the literal, and then work with data_map of this object?. for literals located at pagelayout, those queries will be executed everytime you request a page (if you don't use cache-blocks, i mean).

The idea of admin translations in the admin site is good either. what about provide an interface to work with .ts files?

Saturday 20 December 2008 8:06:41 pm

Hi Maurizio,

I have started developing a translation tool. The basic concept was to enable easy, editorial, multi-user translation collaboration as well as some automated translation management. Some of the tools include source or translation import (so that you can in seconds prepare a file for translation from any language to any language), change highlighting, exports, etc.

This tool would not have solved methodology problems, only facilitate working on *.ts file. Unfortunately, I haven't really finished it and I have no idea when I will. I could share this as soon as I put it to any shape that makes sense for others...

Also, we've covered some common translation issues and approaches here:

Monday 22 December 2008 12:47:30 pm

TS is crap and not a standard like TMX.

This is how TMX markup would looke like it is more suited to what we need.

<?xml version="1.0"?>
<!-- Example of TMX document -->
<tmx version="1.4">
  <note>This is a note at document level.</note>
  <prop type="RTFPreamble">{\rtf1\ansi\tag etc...{\fonttbl}</prop>
  <ude name="MacRoman" base="Macintosh">
   <map unicode="#xF8FF" code="#xF0" ent="Apple_logo" subst="[Apple]"/>
   <note>Text of a note at the TU level.</note>
   <prop type="x-Domain">Computing</prop>
   <prop type="x-Project">P&#x00E6;gasus</prop>
    <seg>data (with a non-standard character: &#xF8FF;).</seg>
    <prop type="Origin">MT</prop>
    <seg>donn&#xE9;es (avec un caract&#xE8;re non standard: &#xF8FF;).</seg>
   <prop type="Domain">Cooking</prop>
   <tuv xml:lang="EN">
   <tuv xml:lang="FR-CA">
   <tuv xml:lang="FR-FR">

Monday 22 December 2008 4:27:34 pm

I know there are some big iusses and limitations on my approach. Carlos wrote well about fetch performance, and there is also some problem in parametrize some variables in the message.

Piotrek thank you for the reply. I will take a look to Addicted contrib.



You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from