[opencms-dev] OpenCMS 6.0-alpha2 Multi-language support

Hartmann, Waehrisch & Feykes GmbH hartmann at waehrisch-feykes.de
Tue Nov 23 13:34:33 CET 2004


Hi all,

we currently develop a LocaleHandler that does not need to have different
folders for each language. It stores the information, which language
currently is selected, in a session variable.
The benefits are:
- no need for language folders and siblings
- jstl format tags (e.g. <fmt:message ...>) work out of the box with the
session variable
- the language can be set via a request parameter
- the language can be read via CmsObject#getRequestContext()#getLocale()

But there are also some drawbacks
- How should one handle language dependent page properties (e.g. NavText)?
We introduced language versions of this properties (i.e. NavText_en) and
modified CmsJspNavBuilder and CmsJspNavElement to work with it. Another way
would be to move such information from properties to page elements, as it is
already done in the XmlContents. But this needs some changes in the core.
What do you think?
- no static export for language specific pages possible
- cookies required
To avoid the need of cookies, we made some minor changes to
org.opencms.jsp.CmsJspTagLink to encode the session id into the url if
cookies are disabled. But this prohibits the use of the tag in a way like
this: <a href="<cms:link>/myfolder/</cms:link>index.html">. What do you
think of integrating this into OpenCms?

Regards,
Stephan

----- Original Message ----- 
From: "Martin Kuba" <makub at ics.muni.cz>
To: "The OpenCms mailing list" <opencms-dev at opencms.org>
Sent: Tuesday, November 23, 2004 11:19 AM
Subject: Re: [opencms-dev] OpenCMS 6.0-alpha2 Multi-language support


> Alexander Kandzior wrote:
> > Benjamin
> >
> > For 1) You must attach the property "locale" to a folder where the pages
are
> > located (or any parent folder).
>
> The missing piece of information here is that then the file
> is displayed *only* in the locale selected by the "locale" property.
> You have to create another folder with different setting of
> the "locale" property, and create a "sibling" of the file
> in the other folder, to see the other languge part of the file.
>
> There is no mechanism which would make sure that such siblings
> exist for each language, so it is questionable whether
> this languages-sibling-locale stuff gives anything
> more than just having separate files for each language.
>
> Martin
> -- 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Supercomputing Center Brno             Martin Kuba
> Institute of Computer Science    email: makub at ics.muni.cz
> Masaryk University             http://www.ics.muni.cz/~makub/
> Botanicka 68a, 60200 Brno, CZ     mobil: +420-603-533775
> --------------------------------------------------------------
>
>
> _______________________________________________
> This mail is send to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://mail.opencms.org/mailman/listinfo/opencms-dev
>




More information about the opencms-dev mailing list