Posted by ryan_courtnage on September 17, 2007 at 7:36pm
Jump to:
| Project: | Address field for CCK |
| Version: | 5.x-2.1 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | ryan_courtnage |
| Status: | closed (fixed) |
Issue Summary
After enabling both the USA and Canada address support, "Unknown Locale name fr_CA" is reported as an error on content creation forms for nodes that use the address field type.
The content does actually get submitted, but the error is annoying.
Comments
#1
Hmm, I'll look into that.
You should know that a user's computer has to be configured for a given language in order to use that language. But if this error comes up, say, when you are entering in a U.S. address with the Canadian module enabled, then that definitely shouldn't happen. I would expect it to come up if you are entering in a Canadian address and don't have French Canadian enabled for your computer.
In Windows, this can be a pain in the butt. Perhaps I should disallow the use of a module by a given user if they haven't setup their computer correctly? Or maybe I should simply give a more friendly warning advising that specially accented characters may not work.
Did you enter in any characters with accent marks? If so, did they store and display correctly?
If you could experiment a bit more, that would be helpful as I'm rather swamped right now.
#2
Since the original poster had no more info on this, and since computers tested with Canada set as a valid locale seem fine, I'm assuming that entering in Canadian addresses from computers without Canada set as a valid locale is the real problem.
All this means is that special characters, such as vowels with accents and so forth do not work when submitted from computers that haven't set up those locales locally. I hope that makes sense. In Windows, for example, you should be able to enable as many locales as you want. So if your company routinely needs to enter addresses from various parts of the world, this should be done so as not to get the error mentioned.
If anyone knows a better way to allow foreign characters AND validate for particular languages, I'm all ears.
#3
I'm having the same problem as the original poster, but I don't think that the problem is the way that my computer is set up. This error only started appearing once I moved my site to the production server. It worked fine on the test server, and I'm using the exact same computer to access the live site.
Could someone explain exactly what this error means?
#4
The server has to have all locales that will be used setup beforehand so that as it processes addresses from various languages, it can use those special character sets for validation. So if your server isn't setup for French Canadian, then when it tries to switch to that character set, it can't. How you setup valid character sets depends on the OS you are using. Consult your manual or Google for that.
#5
Issue more than 6 months old