Sibylle Koczian wrote: > "Ed Leafe" <[email protected]> schrieb: >> On Jan 19, 2009, at 8:29 AM, Sibylle Koczian wrote: >> >>> Dabo Version: Version 0.9.0; Revision ~4846 >> >> I made lots of changes to the handling of unicode this weekend, and >> some of the problems you've described were ones that I know have been >> fixed. If you're using Subversion, can you update to the latest and >> try again? >> > > Updated to rev. 4940. I don't get the DeprecationWarning from > dDataSet.py any more, but both UnicodeWarnings and the question about > saving non-existent changes are the same (except the line numbers for > the UnicodeWarnings). Which doesn't really surprise me, because > dbFirebird.py doesn't seem to be changed. This is probably a > Firebird/kinterbasdb problem: older kinterbasdb versions returned blob > contents as str, not as unicode, and the new version only returns > unicode if the new setting 'type_conv=300' is used. I put this into my > copy of dbFirebird.py, but it wouldn't work with older versions of > Firebird or kinterbasdb. > > I'd be interested to know how well other RDBMS cope with non-ASCII > characters. At the moment I'm not really happy with the Firebird way.
Dabo was developed by english speaking people who do not need to use unicode that much. The unicode handling improved drastically over the last year. I wouldn't be suprised if there are still places in the code which have bugs in unicode handling. If you found such a place, the best thing to do would be to provide a code sample which demonstrates the bugs. This way the bugs can be spotted and fixed most easily. I'm sorry that i as a firebird user didn't see the bug for myself. The simple reason is that i didn't have a need to use blobs in the past. Uwe _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
