Unicode problems, yet again

[Ivan Voras]

John Machin wrote:

> Just a thought: I noticed from the traceback that you are running this
> on a Windows box. Profound apologies in advance if this question is an
> insult to your intelligence, but you do know that Windows code page
> 1250 (Latin 2) -- which I guess is the code page that you would be
> using -- is *NOT* the same as iso-8859-2, don't you?

Yes, I know. The reason I'm doing it on Windows is that the app's 
supposed to be multiplatform, so I'm doing part of development on 
Windows, part on FreeBSD... The agreed-upon codepage is iso8859-2 for 
both. (about the "latin2" term - it really sucks that it's used 
incosistently - for example, PostgreSQL (and I think MySQL) use "latin2" 
when they mean iso8859-2).

> need to deal with Unicode, then set up the encoding explicitly on a
> per-file or per-socket basis. The default ASCII encoding is then there

I didn't know that!

... looks at the manual ... oh, it was introduced in 2.3. I wonder if it 
would work for sockets (though I don't plan to use it now - I've got 
explicit encodings/decodings set up).