pyprojection problem

[Bernhard Reiter]

On Friday 25 January 2008 17:03, Bram de Greve wrote:
> > Adding a str() to each access to parameters solved the problem ...
> >
> > Is this acceptable ? There is no way to have strange encoding problem
> > with those parameters (lat_0, etc.).
> >  
>
> ProjPanel.GetParameters(self) can't do any funny things?
>
> I would suggest to move over the patch to Model/proj.py, as that seems
> to be a wrapper around pyprojection.
> I believe we're OK when you replace line 78 by:
>
>         BaseProjection.__init__(self, map(str, params))
>
> NOT TESTED ;)

Thanks for your suggestions, 
I think I have solved this (see the issue for details).

In general I believe the tactic should be to have a working 1.2.1 where we can 
and then port all internal representation to unicode objects.
Then of course we must make sure to give the libraries what they want,
I guess it will be ascii in the case of proj.

Bernhard

-- 
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/20080127/94d4ec2c/attachment.bin