|
Author
|
Message
|
|
Ulrich L.
|
Wednesday 24 November 2004 1:16:19 pm
Hi,
I set up finally a multilingual site. Translation from admin interface works fine. However, terms like "More information", "Previous" or "Next" which are generated by the template system remain english in all languages (I chose german and french as additional ones). How do I manage to get these words translated? I understand it has to do with the i18n operator, but I don't see how to make it work.
Uli
|
|
Lazaro Ferreira
|
Wednesday 24 November 2004 3:25:26 pm
Hi, i18n lets you translate every hard code string in your templates, so it complements database content translation Look at this doc : http://ez.no/ez_publish/documentation/configuration/configuration/language_and_charset/creating_a_new_translation http://ez.no/ez_publish/documentation/development/extensions/translation
Lazaro
http://www.mzbusiness.com
|
|
Ulrich L.
|
Thursday 25 November 2004 1:33:44 am
Hi,
I find all translations which are required in
ezpublishroot/share/translations/ger-DE/translations.ts
In the siteaccess/de/site.ini.append.php the Regional settings are like this:
[RegionalSettings]
Locale=ger-DE
HTTPLocale=de
ContentObjectLocale=ger-DE
TextTranslation=enabled
However, I don't get the translations, instead the debugger displays several lines like this:
No translation for file(translation.ts) in context(kernel/classes/datatypes): 'Text line' with comment(Datatype name)
No translation for file(translation.ts) in context(kernel/classes/datatypes): 'XML Text field' with comment(Datatype name)
No translation for file(translation.ts) in context(kernel/classes/datatypes): 'Checkbox' with comment(Datatype name)
No translation for file(translation.ts) in context(kernel/classes/datatypes): 'Object relation' with comment(Datatype name) So what can I do?
|
|
Ekkehard Dörre
|
Thursday 25 November 2004 3:05:45 am
Hi, try to chmod them to 755 on a Unix/Linux System, then clear cache. Greetings, ekke
http://www.coolscreen.de - Over 40 years of certified eZ Publish know-how: http://www.cjw-network.com
CJW Newsletter: http://projects.ez.no/cjw_newsletter - http://cjw-network.com/en/ez-publ...w-newsletter-multi-channel-marketing
|
|
Ulrich L.
|
Thursday 25 November 2004 4:27:49 am
Can you please specify what do you mean with "them"? Thanks!
|
|
Ekkehard Dörre
|
Wednesday 01 December 2004 8:35:55 am
Hi, sorry, I was in AI. All files and folders under share. Greetings, ekke
http://www.coolscreen.de - Over 40 years of certified eZ Publish know-how: http://www.cjw-network.com
CJW Newsletter: http://projects.ez.no/cjw_newsletter - http://cjw-network.com/en/ez-publ...w-newsletter-multi-channel-marketing
|
|
Ulrich L.
|
Saturday 04 December 2004 9:00:17 am
Hi Ekke,
I did exactly what you told me, however without success so far: I still see the emglish hardcoded phrases on the german and the french site.
What else can be wrong? P.S. What's AI? Amnesty International...?
|
|
Ulrich L.
|
Tuesday 07 December 2004 6:42:21 am
While I'm getting deeper and deeper into ezpublish, with good results, I still need and answer how to make i18n work.
I described above what i have done so far. What do I have to do differently to make it work?
I am grateful for any help.
|
|
Ulrich L.
|
Monday 13 December 2004 7:51:27 am
Hi,
my problem is described above very precisely.
I don't manage to solve it on my own.
What can I do?
|
|
Alexandre Cunha
|
Monday 13 December 2004 3:21:09 pm
Hi Ulrich As I understund, your problem is only the translation of harcoded texts in templates, right ?
Ok, lets see this example:
- open a template file, for instance, <your ezp350rc2 installation>/design/base/templates/content/search.tpl
- locate the line with
<h1>{"Search"|i18n("design/standard/content/search")}</h1>
- that means the word "Search" must be translated acording your siteaccess language definition. The word is tranlated if any tranlation is avaiable on the translation.ts file for the language
- now locate the file with translations. Open the file <your ezp350rc2 installation>/share/translations/ger-DE/translation.ts
- locate something like "<name>design/standard/content/search</name>" and see if you have a block for "Search"
- if not, create a block like this
<message>
<source>Search</source>
<translation>Suche</translation>
</message>
- save the file, clear the cache and test your site. The translation for the word "Search" in the context "design/standard/content/search" is done. I wish this helps.
http://AlexandreCunha.com
|
|
Ulrich L.
|
Tuesday 14 December 2004 12:29:10 am
Yes, I understand how i18n should work... However, it doesn't do on my site. This is a wizard generated "shop" site. I made it multilingual (with the help of Luke, thanks!). The content translation can be switched smoothly, but the hardcoded strings remain english. I described this above: Words like "More information" (e.g. shown while giving line view of a product) remain english even when accessing the german or french siteaccess. I can't find anything wrong in the wizard-generated templates (of course...), and the .ts-files contain all translations as they should do. Everything looks fine here, but doesn't work... So it has got something to do with the site setup, but I don't get the point. What are the debug warnings telling me (stated above)?
|
|
Ulrich L.
|
Tuesday 14 December 2004 11:11:52 am
Hi,
so I try it this way: can anybody give me examples of the appropriate settings in the configuration files (site.ini-files and so on) which make i18n running?
|
|
Ulrich L.
|
Thursday 16 December 2004 1:48:54 pm
While I'm now very sure my settings are o.k. I wonder wether my problems have something to do with this reported bug:
http://www.ez.no/community/bugs/i18n_operator_problems_with_comments Is this possible (I'm running 3.4.4)? Do I have to take care of any special charset settings for german and french translations?
|
