|
Rob Rob
|
Tuesday 15 February 2005 9:14:42 am
Nice site, nice example The documentation is my problem in the moment. How you handle the translationwork, do you seperate the languages totally or can you switch between the languages easily? In other words can you publish one text (eg english) for all languages or you need to switch to the next language(eg french) and edit the article again? I am thinking about news and if it possible to create one article for all languages? Thanks
|
|
Ekkehard Dörre
|
Tuesday 15 February 2005 3:27:00 pm
Hi Rob, <i> Is there a solution about browser recognition or geotargeting, I cant't find it in the forum</i>
Browser Recognition:
http://ez.no/community/contribs/template_plugins/ezbrowsersniff_operator
Geotargeting with help of Sörens:
http://ez.no/community/contribs/3rd_party/extension_phpadsnew_pubsvn
Most information is found via:
http://ez.no/content/search?SearchText=multilingual 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
|
|
Nicolas Heiringhoff
|
Wednesday 16 February 2005 3:29:35 am
Hi Rob, basically you have to create a separate siteacces in the "settings/siteacess" directory like "plain", "plain-fr", "plain-eng". Then you must edit the site.iniappned.php files of these separate siteaccess and match the access url to the siteaccess of each language
http://www.heiringhoff.de
|
|
Simon Phillips
|
Wednesday 16 February 2005 10:15:52 am
The most useful documentation by far is http://www.ez.no/ez_publish/documentation/configuration/configuration/language_and_charset/how_to_setup_a_multilingual_site I was able to follow that and now have a site in 4 languages. However, I'm stuck in trying to add a language menubar. Since the node translation information is only available at the view template level, I can't access it from within pagelayout.tpl, which is where I want to display it. How have you guys got around this? Obviously, I could always display language flags even if a translation isn't available, but that isn't ideal. Simon
|
|
Simon Phillips
|
Wednesday 16 February 2005 11:01:48 am
To reply to myself... You need to use the fetch template function to retrieve the node details at the pagelayout level. I use subdomains to determine the different languages.
{* Code to show list of translations *}
{let languages=hash('eng-GB',concat('<img class="flag" alt="English" src=',"en.gif"|ezimage,'/>'), 'esl-ES',concat('<img class="flag" alt="Spanish" src=',"es.gif"|ezimage,'/>'), 'fre-FR',concat('<img class="flag" alt="French" src=',"fr.gif"|ezimage,'/>'), 'ger-DE',concat('<img class="flag" alt="German" src=',"de.gif"|ezimage,'/>'))
let lang_sub=hash('eng-GB','www','esl-ES','es','fre-FR','fr','ger-DE','de')
let domain='.gv2006.org.uk.local/'
thisnode=fetch(content, node, hash(node_id, $module_result.node_id)) }
{section show=$thisnode.object.current.translation_list|count|gt(0)}
{section var=translation loop=$thisnode.object.current.translation_list}
<a href={concat('http://',$lang_sub[$translation.language_code],$domain,$module_result.content_info.url_alias,'/(language)/',$translation.language_code)}>{$languages[$translation.language_code]}</a>
{/section}
{/section}
{/let}
|
