TestNonAsciiColumnName.test (Re: WIP-pyshapelib-Unicode issues)

[Bernhard Reiter]

On Wednesday 09 January 2008 11:47, Bram de Greve wrote:
> If possible, can you guys test it to identify any further issues?  You can
> use the WIP-pyshapelib-Unicode branch "out of the box", as no merge with
> the trunk is necessary (I did that for you).
>
> Known issues:
>
> * {test_load|test_load_1_0}.TestNonAsciiColumnName.test:
>
> the column name Fläche is giving us troubles.  Not in dbflib itself, as it
> is handled correctly over there, but apparently it is not encoded to UTF-8
> when written to the session XML, causing the test to fail.  I'm not
> familiar with this issue, so if anyone can help, please feel free =)

This is an artifact of the now tried conversion to unicode for dbflib.
Note that the testsuite still runs in internal_encoding "latin-1"
by default.

Try running it with "unicode" as internal_encoding and you will see
that the particular test that fails is okay now (but others fail): 

 python runtests.py --internal-encoding=unicode test_load_1_0


-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.intevation.de/pipermail/thuban-devel/attachments/20080214/c1cd2378/attachment.bin