[opencms-dev] Multilingual sites - Browser's AcceptedLanguages

[Christian Steinert]

>> >> AFAIK you need individual siblings for each language. And in order to
>> >> create them you have to either create them by hand individually
for each
>> >> language, or you have to write sth. that hooks more deeply into the
>> >> system (like an own resource type that auto-creates/deletes/moves
>> >> several siblings around whenever a new resource is created).
> >
> > Ok, we will see what I figure out when I look deeper into this. Thanks!
> >
> > /Peter


Just to be precise here: There is no need to use *siblings* for i18n.
But currently you need to have an individual resource header per
language, because each language needs its own "carrier" for the file's
properties. So technically, you don't need siblings, but you need either
siblings or replicas or some self-invented mechanism to store the file
properties for each language of a given page.

And - yes, what you do is very similar to what I do. I have individual
files for each language under
  /sites/default/de/foo/bar.html
  /sites/default/en/foo/bar.html
and so on. These files are not siblings of each other but just
independent pages. Only my templates and the Java code behind them knows
that they have some relation. Opencms doesn't. I don't work with the
__locale paramerter at all - as long as properties cannot be properly
translated, I don't see much use in using it.

Regards
Christian


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3269 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20060717/0b02df02/attachment.bin>