The trick with cultures is knowing what happens when, the reasons why - and understanding where your code fits into the cycle.
There's a negotiation that happens between the browser and the server - where they quiz each other about what cultures the browser has been configured with - and what the server can provide. Note: Often users don't know how to change or set the culture - so if they have installed their browser from a default, non-locale aware source, it'll report the wrong culture. ie: Many browsers have en_US as a default (because it was installed from a fast US server an a en_US package) - even though the user is actually on a es_AR culture OS somewhere in Argentina. The site will also have a list of cultures that it supports (you don't often have every language available). sf can auto-magically workout which culture to use using negotiation between what the site supports and what the user understands - checkout http://www.symfony-project.org/book/1_2/13-I18n-and-L10n#chapter_13_sub_determining_the_culture_automatically for more info. You will however still need to provide a way for users to change culture due to the inaccuracy of browser cultures. On Mon, 26 Oct 2009 11:21:42 +0100, HAUSa <jeroen_heeft_behoefte_aan_r...@hotmail.com> wrote: > > Is it possible to set multiple cultures for users? For example first > the culture FR, then the culture EN. > When a Propel object is not available in FR, it automatically takes > the EN value. > > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
