Re: [Gvr-devel] which version of wxPython: ansi or unicode

[<and...@ns...>]

On 5/10/05, stas Z <sta...@gm...> wrote:
> On Tue, 2005-05-10 at 11:18 -0300, André Roberge wrote:
> > Hi everyone!
> >
> > This question may be more relevant to Peter and Stas.  Which version of
> > wxPython do you recommend: the ansi version or the unicode one.
> > Looking at the wxPython site, it looks like the ansi version is the most
> > portable (in terms of operating systems).  However, I thought that the
> > unicode one would be more portable (human language wise).
> I recall to have read somewere at the wxpython mailinglist that the ansi 
> version
> would be deprecated very soon.
> I agree with Peter that unicode would/should become the standard.
>
> > I'm planning to upgrade my Windows system to wxPython 2.6 tonight (in
> > approximately 8 hours) and would *really* appreciate your input before 
> > then.
> > (This will mean that much work will be required to get rur-ple working
> > again!)
> Why do you want to upgrade your version of wxpython?
> It seems to me that you should fix the unicode problem because, and
> don't get angry with me, it's a bug in rur not in wxPython.
> Upgrading just because it seems to fix something you broke is not the
> correct way.
> Versions before 0.8.5 worked perfectly on all platforms, with a number
> of different wxPython versions.
>

This is a very good point.  What I was proposing to do was attempting to
"solve" two problems at one.

Taking a deep breath:
---
I got a message on some other list about
rur not being able to import the appropriate version of wxPython, coupled
with issues with wx-namespace - which I thought was because I was
requesting version 2.4 and, failing that, was reverting to an assumption 
that
earlier wxPython versions would be used (with the old wx-namespace
convention) - which would not be the case for a user with wxPython 2.6.
--- time to breath in again :-)

Ok, I need to solve the broken version issue first.  See 1.) below.
====
Back to the problems observed by Stas - which I can not reproduce :-(
(Stas mentioned these in an other message, but they may have been observed
by other, silent victims)
Could you, Stas, possibly try the following:
1.) if you look in the folder structure for rur-ple, you will find the 
following
rur_py/languages/french.py
if you could replace in that file /= "/= u"/
I believe that should solve the language issue everywhere (I hope!).
If so, I'll make sure to fix it everywhere else...

2.) problem with being unable to run the user-programs.  I suspect that
this is a line-ending related issue that gets created when I add
line number information so that instructions can be highlighted.
Could you check, pleeeease, by going in parser.py, and adding
a "return code" statement on line 55, thereby bypassing
the whole linenumber thing.  It will break various cosmetic issues,
but should still work just the same.

3) As for the invalid world file issue, I strongly suspect that it is again
a line-ending issue.  I'll have to have a closer look at the world file
you sent me.

I will be away until early next week, due to work-related duties.
I will not be able to work on rur-ple during that time, but I will
try to check my mail regularly.

André

> Stas