Thanks, both are accepted, but, from the scientific point of view 'ca' is more precise and we will save a few bytes if the es_CA files are not present ;)
Merry Christmas and I won't bother you with more localization issues... until next hour or so... ... just kidding :) Bruno > okay, now in CVS; > > **_ca.properties > (both) > I read your post, that includes a es_ca > and so I took it... :-P > > Regards, > Matthias > >> -----Original Message----- >> From: Bruno Aranda - Dev [mailto:[EMAIL PROTECTED] >> Sent: Friday, December 24, 2004 1:09 PM >> To: [email protected] >> Subject: Localization for catalan (ca / es_CA) >> >> >> You know my copy and paste keys are in holidays... :P >> >> Yes, both files should be renamed to *_ca.properties to >> follow the standards. But the current file >> Messages_es_CA.properties should be removed as it is not the >> catalan translation but the spanish one (a mistake here). The >> file in the JIRA called Messages_ca.properties is OK and it >> is the file that should be in the core. >> >> This xmas, Santa will bring a localization nightmare for >> everybody... :) . But here, we don't believe too much in >> Santa Claus but in the Three Kings... and its camels... >> >> Bruno >> >> >> Sorry, my last post had a wrong topic. This was the message: >> > >> > no problem, I like to laugh, since it is xmas... >> > :) >> > >> > ok, >> > >> > in fact, you said Catalan language is ONLY working >> > in MyFaces examples with the file: example_messages_es_CA.properties >> > and not in Myfaces *core* with the file: >> > Messages_es_CA.properties >> > >> > okay... and you said catalan is an own language, >> > >> > so I now guess we must change *both* files to ***_ca.properties >> > >> > Right? >> > >> > Regards, >> > Matthias >> > >> >> >> >> Well, canadian is not a language itself. I think they mostly speak >> >> english and french (en_CA, fr_CA). The domain for canada >> is 'ca' but >> >> it is not the language identifier, as it does not exist. You can >> >> check the ISO language codes for that matter. Domain codes don't >> >> match language identifiers in many cases, as there are countries >> >> which don't have an own language. For example, Argentina >> with domain >> >> .com.ar use the language id es_AR, as they speak a >> different variety >> >> of Spanish. I've always used the code ca for catalan and >> >> browsers understand it well and show the pages in catalan (if >> >> the browser is properly configured, of course) :-) >> >> >> >> Regards, >> >> Bruno >> >> >> >> > mmm, I am not familar to the catalan issue, >> >> > but I guess a file calles Messages.properties_ca >> >> > is for Canadian ? >> >> > >> >> > Regards, >> >> > Matthias >> >> > >> >> >> -----Original Message----- >> >> >> From: Bruno Aranda - Dev [mailto:[EMAIL PROTECTED] >> >> >> Sent: Friday, December 24, 2004 12:09 PM >> >> >> To: [email protected] >> >> >> Subject: Localization for catalan (ca / es_CA) >> >> >> >> >> >> >> >> >> Hi, >> >> >> >> >> >> I've seen in the CVS that the file for messages in catalan >> >> >> (current >> >> Messages_es_CA.properties) is the spanish file (Messages_es), >> >> >> so there is a mistake here. I've checked the catalan file >> >> in the ASF >> >> >> JIRA MYFACES-59 and it is OK. The message files for the >> >> examples are >> >> >> OK, except if we apply the next paragraph :P >> >> >> >> >> >> The catalan language is more commonly writen with the >> ISO language >> identifier 'ca' (Messages_ca, for instance) because >> >> catalan is not a >> >> >> dialect from spanish, but it is a different latin language >> >> (such as >> >> >> french or italian). In my browser (Firefox), for example, when I >> configure the catalan language it looks for the 'ca' identifier. >> >> >> >> >> >> Language codes -> >> http://ftp.ics.uci.edu/pub/ietf/http/related/i> > >> so639.txt >> >> >> >> >> >> >> >> >> Thanks, >> >> >> >> >> >> Bruno >> >> >> >> >> > >> >> >> >> >> >> >> >> >> > >> >> >> >> >
