You're changing the rules :) The idea is that the site has a default language (e.g. en_GB) (if you want to use locality), the user's browser dictates which language the user sees, however the site falls back to the default language if their's is not available.
There is a language flag link at the top showing you which languages are available. This will re-render the current page, but set a language cookie that overrides your browser language. (This can also be a separate page completely.) Another option is to redirect a user to a page where they must select the language they wish to see the site in from a list of valid languages. This is then set within their session as well as a cookie for future visits to the site. Each of the above is fine, but one just examines the settings for your browser and renders the site approriately. A good example of this is www.sony1.net [EMAIL PROTECTED] wrote: > Adam Reynolds wrote: > >> It should never be dealt with through the addition of a ?lang=en >> >> > I would not go so far as saying that. I work in a company that installs > the browsers and for that install package they use the original > language of that company. If a cookie is not found I rather see a page > where I can choose the language then a weird language page where I have > to look for the place where to change the language. Probably this is a > personal opinion. > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev -~----------~----~----~----~------~----~------~--~---
