4 Commits

Author	SHA1	Message	Date
Mika Bostrom	04c345ae1f	Use a different "unicoder" for db strings ... It seems that running encoder.encode() on a latin1/latin9 string results in, yes a bloody UnicodeDecodeError. Decode error on .encode()... Really. This way the modification from non-unicode string to real unicode appears to work better.	2010-01-21 21:46:14 +02:00
Mika Bostrom	dda00b6b10	Catch character encoding errors	2010-01-21 21:31:19 +02:00
Mika Bostrom	e915b0b62c	Allow to bypass codec ... If the system (display) locale is UTF-8, there is no need to encode to either direction. In fact, running the .encode() routine appears to mangle a valid UTF-8 string to a worse condition, effectively breaking it.	2010-01-21 21:23:13 +02:00
Mika Bostrom	34bf2bd8e9	Use better function name	2010-01-21 18:12:45 +02:00