TEP 001: Fully switch to unicode (was: [Thuban-list] Problem with Thuban in Ubuntu)

[Didrik Pinte]

On Wed, 25 Apr 2007 10:46:38 +0200, "Bernhard Reiter"
<bernhard at intevation.de> said:
> Thuban Enhancement Proposal 001:
> (20070425ber)
> Bernhard Reiter <bernhard at intevation.de>
> 
> Fully switch to use of python unicode objects internally.
> Throw out special translation modes for other internal encodings
> like utf8 or latin1.
> 
> Rational:
> * Simplification: It would require less code and less branches.
> * Fixes problems of Thuban 1.2.0 where not all return values from wx
>   in a unicode build are already translated back to internal encoding.
> * No need to keep other encodings around as the main targets GTK and
> Windows
>   can build wxPython in unicode well and it seems to be default,
>   e.g. in Debian since wxPython 2.5.4.1.
> 
> How to do it:
> Test the already build in internal_encoding = "unicode", if necessary add
> a comand line version.
> 
> Use wxversions to hard-select 2.6-unicode, also test for wx.USE_UNICODE
> and bail out if we cannot have this.
> 
> Remove code in Thuban/__init__.py and Thuban/UI/__init__.py and change
> the 
> places where that funcation have been used.
> 
> Please all comment.
> Bernhard

This sounds a very good idea. Especially that now we have correct
support of 
unicode in pyshapelib thanks to Bram.

Let's do it !

Didrik