Multilanguage website

Author Message

Heiner Wurbs

Thursday 13 January 2005 6:58:14 am

Hi,
I want to build a multilanguage website. I read already the introduction
http://www.ez.no/ez_publish/documentation/configuration/configuration/language_and_charset/how_to_setup_a_multilingual_site but there could be some problems for me. I'm using different sites in one ez installation, so siteaccess is used to distinguish between them and not between the language.
Are there other possibilities to build a mlw?
Regards,
heiner

Sven Berg Ryen

Thursday 13 January 2005 8:17:50 am

Hi Heiner!

Are you planning to translate all your content to another language, or simply provide parts of your content in multiple languages?

Cheers,

Sven Ryen
sven.ryen at maxus.no

Heiner Wurbs

Thursday 13 January 2005 9:13:38 am

hello sven, thanks for your answer!
yes, every content should be translated. at the moment I installed it as described in the article above, and I'm using s.th. like

[SiteAccessSettings]
AvailableSiteAccessList[]=site1
AvailableSiteAccessList[]=site2
AvailableSiteAccessList[]=mlw_site3_de
AvailableSiteAccessList[]=mlw_site3_pl
AvailableSiteAccessList[]=mlw_site3_admin
AvailableSiteAccessList[]=site4

This siteaccess works, but I would prefer another solution, where the language distinction is more seperated from the siteaccess list. The problem is also, that I had to copy all other siteaccess-related files e.g. override.append.php etc to the second language siteaccess directory.

But there is of course another problem, when I inserted the polish content. Every special polish character is shown on the user website like

a polish test śż

Do you know another solution, is there something wrong?

Best regards,
Heiner

Sven Berg Ryen

Thursday 13 January 2005 11:03:20 am

It's actually quite easy to rewrite eZ publish to avoid having to set up one siteaccess per language. I did it once back in 3.2, and it worked great.

If I'm not totally wrong, I also made a module that took care of changing the language, plus I had the user's preference stored as a cookie.

This required adding 10 lines or so to 3 or 4 of the files in the kernel, so it was a bit of a "hack".

I'd like to see this addressed more intelligently in the kernel in a future upgrade. 3.6? :)

Cheers,

Sven Ryen
sven.ryen at maxus.no

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.