> -----Original Message----- > From: Eric Dahnke [mailto:[EMAIL PROTECTED] > Sent: Friday, August 27, 2004 1:53 PM > To: Struts Users Mailing List > Subject: ApplicationProperties_es_ES > > > > Hello list, > > > We're building an internationalized site, and we're having an > issue with > locales and resource bundles. If we have two specific > resource bundles for > Spanish from Spain (ApplicationProperties_es_ES.properties) > and Spanish from > Argentina (ApplicationProperties_es_AR.properties), one would think a > browser arriving with a locale/user-agent of es_MX would be > caught by one of > the two es_* properties file, but infact es_MX gets the > default English > properties file, unless there is specifically a > ApplicationProperties_es.properties file. > > Is this the expected behavior?
Yes, you could try a properties file called es, without the country and see if that works. I think it should. When I first saw this, I thought it was odd too... then I remembered something someone said about spanish, in particular, and may be true in other languages as well, and it made sense. Seems that Spanish has a lot of local euphemisms that cause some interesting confusion. One place has one word used for a woman of good repute for instance, while 10 miles down the road, it's used for a woman of ill-repute. Well, if that's true of more then just Spanish, then it makes sense that the i18n stuff won't assume that es_MX and es_ES are the same, or any other language/country code either for that matter. > > > Thx > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
