On 30 Dec, Alexander Bokovoy wrote:
> It'll create unnecessary complexity.
> Saving locale preference as URI will add another feature: if one want to
> get, for example, German translation of interested article, he/she just
> replaces only first element in path (it could be done via pull-down menu
> on the page) and nothing else. (Of course, if site is supporting German
> version). Also old browsers will work without problems too.
> As for browser preferences, there is another issue. Netscape
> Communicator, for example, has 'en' by default even in many localized
> versions, and many international users don't change this setting at all
> (many of them even don't know about it). Automatically selecting site
> version by Preffered language: field in header will work bad in this
> situation.
Ok, good point. However, another option here would be to
support both methods. If MidgardMultiLang is set on in
httpd.conf (maybe it would be more intuitive to configure
this in Midgard's Host table instead?), the Midgard would
use the /LC/page URIs, otherwise the $midgard->locale
could be manipulated in the PHP end.
Would this approach cause problems with implementation?
> Alexander Bokovoy
/Bergie
--
-- Henri Bergius -- +358 40 525 1334 -- [EMAIL PROTECTED] --
http://www.iki.fi/Henri.Bergius
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
