Translation / Internationalization

Next topic

Author	Message
John Hoskins	Tuesday 08 April 2003 2:34:09 pm Trying to get support for several languages going on my test site. So I added a new language under admin / setup tab / translations and chose one and hit new. I go into one of the articles on the site and add a new translation for the document and publish it. 1. So the english version shows at /content/view/full/217, where is the norwegian one I published? 2. How does a user get setup so that they come in and get the language that they want? Is that a browser thing? And how can I allow users to choose a translation 3. What ini file needs to be changed to show things like Hebrew, Arabic and stuff that does not come close to using latin? What about Swedish, German, and other languages that use mostly latin but some other funky characters? 4. If a site has some content in a language but it is all in english, will it show up in english if there is no translation available? Is this a behavior that is settable? 5. It seems like there is no easy way to tie a version of the main (english) article to a translation. When I look into the ezcontentobject_name table, I see version numbers for translations but they never appear when I edit the translations. Further, it seems like translation are published in tandem and are not serperately controlled. This is the behavior that I need for my project. New content is written in english and put into a workflow. Site manger gets notice that there is new content. Site manager assigns translation duty for that document to available people. Site manger can publish english version while the translations are coming. As translation are coming in, they are published. If a correction to a translation is needed it can be updated seperately from the english version. Each translation is tied to a version of the english articled. If the english version is updated, the site manager assigns updating of the translation and the translators use their last version as the start of their edits. I know I need to do some workflow stuff but is the current presentation of translation, coding login in the edit pages or login lower down?
Jan Borsodi	Friday 11 April 2003 7:12:43 am 1. /content/view/full/217/nor-NO should show it, however it seems like a bug with these syntax with the 3.0 release. 2. Currently there's no personality system in eZ publish. You will have to manually tweak the index.php file to handle language changes, for instance based on browser language or a user selectable language in a custom module. 3. To get hebrew, arabic etc. you will have to use the UTF-8 encoding. You will have to change this in settings/i18n.ini which defines the core charset for the site. With UTF-8 (Unicode) you can get most languages in the world on the same site at the same time. 4. Yes, that is the purpose. 5. Translations are not versioned independently. If you want need that feature I can recommend using different objects for different languages. You will then link in the various languages using related objects. This is also the best solution if you want translations made while the main language is published, for instance the site manager would tell the translators to copy the original object and create the translations. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq
John Hoskins	Friday 11 April 2003 8:15:01 am Thanks for the reply. Want to understand further your reply. 4 & 5. So if I do what you suggest in 5. Then the feature in 4 will not work without custom coding? 3. If I put content in using Latin in i18n.ini and then change it to utf-8 will that stuff be screwed up. Is that setting central to the way the system understands its internal content or just is a display function? 2. So I either need to do browser detection and/or have a global variable that is set to keep language together.

Author

Message

Tuesday 08 April 2003 2:34:09 pm

Trying to get support for several languages going on my test site.

So I added a new language under admin / setup tab / translations and chose one and hit new. I go into one of the articles on the site and add a new translation for the document and publish it.

1. So the english version shows at /content/view/full/217, where is the norwegian one I published?

2. How does a user get setup so that they come in and get the language that they want? Is that a browser thing? And how can I allow users to choose a translation

3. What ini file needs to be changed to show things like Hebrew, Arabic and stuff that does not come close to using latin? What about Swedish, German, and other languages that use mostly latin but some other funky characters?

4. If a site has some content in a language but it is all in english, will it show up in english if there is no translation available? Is this a behavior that is settable?

5. It seems like there is no easy way to tie a version of the main (english) article to a translation. When I look into the ezcontentobject_name table, I see version numbers for translations but they never appear when I edit the translations. Further, it seems like translation are published in tandem and are not serperately controlled.

This is the behavior that I need for my project. New content is written in english and put into a workflow. Site manger gets notice that there is new content. Site manager assigns translation duty for that document to available people. Site manger can publish english version while the translations are coming. As translation are coming in, they are published. If a correction to a translation is needed it can be updated seperately from the english version. Each translation is tied to a version of the english articled. If the english version is updated, the site manager assigns updating of the translation and the translators use their last version as the start of their edits.

I know I need to do some workflow stuff but is the current presentation of translation, coding login in the edit pages or login lower down?

Jan Borsodi

Friday 11 April 2003 7:12:43 am

1.
/content/view/full/217/nor-NO should show it, however it seems like a bug with these syntax with the 3.0 release.

2.
Currently there's no personality system in eZ publish. You will have to manually tweak the index.php file to handle language changes, for instance based on browser language or a user selectable language in a custom module.

3.
To get hebrew, arabic etc. you will have to use the UTF-8 encoding. You will have to change this in settings/i18n.ini which defines the core charset for the site.
With UTF-8 (Unicode) you can get most languages in the world on the same site at the same time.

4.
Yes, that is the purpose.

5.
Translations are not versioned independently. If you want need that feature I can recommend using different objects for different languages. You will then link in the various languages using related objects.
This is also the best solution if you want translations made while the main language is published, for instance the site manager would tell the translators to copy the original object and create the translations.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

John Hoskins

Friday 11 April 2003 8:15:01 am

Thanks for the reply.

Want to understand further your reply.

4 & 5. So if I do what you suggest in 5. Then the feature in 4 will not work without custom coding?

3. If I put content in using Latin in i18n.ini and then change it to utf-8 will that stuff be screwed up. Is that setting central to the way the system understands its internal content or just is a display function?

2. So I either need to do browser detection and/or have a global variable that is set to keep language together.