On 20.12.2014 19:35, Tom Lane wrote:
> Tomas Vondra <tv@fuzzy.cz> writes:
>> On 20.12.2014 19:05, Tom Lane wrote:
>>> I am betting that you recreated them differently from before.
>
>> Aaaaand you're probably right. Apparently, I recreated them like this:
>
>> $ localedef -v -c -i cs_CZ -f WIN-1250 cs_CZ.WIN-1250
>
>> but the correct way seems to be this:
>
>> $ localedef -v -c -i cs_CZ -f CP1250 cs_CZ.WIN-1250
>
> Interesting. Apparently, instead of failing outright on an unrecognized
> charmap name, localedef just substituted ASCII and plowed ahead. Bad dog.
Not really. It's rather about abusive owner of the dog, using '-c' to
force the dog to create the locale even when there are warings:
# localedef -i cs_CZ -f WIN-1250 cs_CZ.WIN-1250 character map file `WIN-1250' not found: No such file or directory no
outputfile produced because warnings were issued
In my defense, I've been using verbose mode, and that produces a lot of
warnings like 'non-symbolic character value should not be used' (which
gets ignored in non-verbose mode) and thus missed the one important one.
regards
Tomas
