[opencms-dev] Multilingual sites - Browser's AcceptedLanguages
Christian Steinert
christian_steinert at web.de
Mon Jul 17 17:30:43 CEST 2006
> -----Ursprüngliche Nachricht-----
> Von: The OpenCms mailing list <opencms-dev at opencms.org>
> Gesendet: 17.07.06 13:47:38
> An: The OpenCms mailing list <opencms-dev at opencms.org>
> Betreff: Re: [opencms-dev] Multilingual sites - Browser's AcceptedLanguages
> opencms-dev-bounces at opencms.org wrote on 17-07-2006
> 13:19:16:
>
> > I don't see any way of storing more than one value in a file property.
> > Whereas a page body can have several versions in more than one language
> > I don't see any way of storing one file property (say: "Title")
> in one
> > file in more than one language.
>
> If I understand it correctly properties are meant
> to be used for configuration
>
> data which differ between siblings - or in other words
> the properties configure
>
> the sibling they belong to. If this is correct you
> are trying to go against
>
> the paradigm of OpenCms.
>
> One of the properties is the locale - how much sense
> would it make to be able
>
> to switch between several locales in some sort of
> editor in order to fill in
>
> the value of the locale property ?
>
>
> If you want to configure stuff in a locale dependant
> way I guess it could be
>
> done via xmlcontent where you map the properties you
> desire to acess through
>
> the xml editor and use the language switching mechanism
> there.
>
>
> There are several of the xmlcontent examples that
> come with OpenCms where
>
> you can edit the "Title" property in this
> way.
>
>
> Note that if you afterwards set the affected property
> through the property
>
> dialog it will override the xmlcontent (until next
> time you save it - then it
>
> reverts to the value in the xmlcontent)
>
>
> Cheers,
>
>
> Carl
>
Dear Carl,
thanks for your reply.
You certainly have a point when saying that xmlcontent is supporting structured data in a translateable way.
But I am using currently using xmlpages, where you have to rely on file properties to be able to have navigation-related information at all.
In that case xmlpage would also go against the paradigm of opencms...
Well in any case - you certainly got me thinking about xml-content. Until recently this hadn't been an option for me, because the html editor had too little functionality, but I think that has changed with 6.20.
Regards
Christian
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
More information about the opencms-dev
mailing list