Hello! On Wednesday 18 March 2009 21:51:10 Roger Binns wrote: > > Tcl, Python and other langs have different unicode implementations. The > > realizations are more simple than ICU library but millions of > > applications are using these. I'm will glad to see Tcl/Python/etc. > > unicode implementation in SQLite. > > Speaking for Python, you can trivially hook the Python unicode support > into SQLite if you use pysqlite or APSW. However if you think the > builtin Python Unicode support is good then you are mistaken :-) See > http://www.cmlenz.net/archives/2008/07/the-truth-about-unicode-in-python
Yes, python and tcl unicode implementation is not good for me and I'm prefer version coded by Ioannis. But any implamentation may be better than no unicode support. ICU for small devices is nonsense. And ICU compilation is not trivial for some platforms. > Python uses UTF16 or UTF32 internally for Unicode (a compile time > option). It isn't unreasonable to expect developers who are making > heavy use of ICU like functionality (ie enough for performance to be > noticeable) to set the default database encoding to UTF16 which means no > encoding conversions while using ICU. There may be other such "fast > path" optimizations to improve performance when using ICU. But it's not enough for many causes. SQLite has native encodings UTF8 and UTF16 and so unicode extension must supporting these too. Did you know good and small unicode supporting library? I did try to find this in debian linux but I didn't find. Best regards. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
