Hi Joose
I used option 2 for a large site, with a complete user request space available in all langages. If some content is not available in some language, I put an explicit mention about the missing translation on that page, plus a text in some other langage.
For instance: this page is available in french, german, italian and english, but not rumantsch; so there's a mention:
http://www.gallerie-ph.ch/rm/events/construct-sonor/klanginstall/index.html
All this handled thru Linkrewriter and i18n message catalogs, so there is no link manipulation needed in the XSLT. By the way: the linkmap gets translated in each language also, of course. The message catalogs are generated.
--
Olivier
Joose Vettenranta wrote:
Hi,
I came to think what would be the best way to make site accessible with several languages..
Option 1:
Make a localeaction which saves locale information to session/request/whatever.
/info.html -> language depens on locale
Option 2: Make locale available from URI:
/en/info.html /fi/info.html ...
Option 3: Keep locale in URL:
/info?locale=en /info?locale=fi
What is best practise (or good) ..
I was thinking Option 1 would be nice, but how does proxys and caches know that language has changed? so perhaps option 2 would be nice, but then again, making links in XSLT is not that nice. and option 3 is ugly =)
What do you think?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
