wxlua-users

[wxlua-users] Unicode Problem and the Copyright symbol ((c))

[Ryan P. <rpu...@gm...>]

When I wxluafreeze a script that has a Copyright symbol (c), the application
quits right away with no error or anything. I am using it in an about box
and I am just wondering if it has to do with Unicode at all. I am using the
prebuilt wxluafreeze from the 'bin' directory and I have built it myself as
well. I get the same result. Also, it works great when ran with "wxLua" and
not frozen. For now I am just changing the (c) to (c).

Any thoughts would be greatly appreciated.
-- 
Regards,
Ryan
RJP Computing

Re: [wxlua-users] Unicode Problem and the Copyright symbol ((c))

[John L. <jla...@gm...>]

On 1/22/07, Ryan Pusztai <rpu...@gm...> wrote:
> When I wxluafreeze a script that has a Copyright symbol (c), the application
> quits right away with no error or anything. I am using it in an about box
> and I am just wondering if it has to do with Unicode at all. I am using the
> prebuilt wxluafreeze from the 'bin' directory and I have built it myself as
> well. I get the same result. Also, it works great when ran with "wxLua" and
> not frozen. For now I am just changing the (c) to (c).
>
> Any thoughts would be greatly appreciated.

I have tried this in the minimal.cpp sample using MS VS2005 and (c)
does work in the about dialog there. Why it doesn't work in wxLua is
probably because of the wx2lua and lua2wx string conversion functions
in modules/wxlua/include/wxlstate.h.

This has been discussed before, but with no resolution. The problem is
that people make suggestions for changes to make it work for them, but
would break things for other people. I do not understand much about
unicode or even UTF8 strings other than a cursory knowledge so I
cannot help much. I presented a summary of the different suggestions
on the mailing list, but nobody seemed to know definitely what was
right.

see "wx2lua & Unicode was Re: [wxlua-users] Problem in using Turkish
in wxLua scripts"

I think we have two competing needs, unicode for international
languages and UTF8 for ??? Can the two be mixed? I dunno.

Regards,
    John Labenski

Re: [wxlua-users] Unicode Problem and the Copyright symbol ((c))

[John L. <jla...@gm...>]

I don't have time to read this now, but this was just posted on the
wx-users mailing list in response to this message "Using Chinese (not
i18n)".

http://lists.wxwidgets.org/cgi-bin/ezmlm-cgi?8:msp:94195:hljgalnnllihfkjijnlh

Maybe the programs wxluafreeze, wxlua, etc need to have command line
switches to allow you to specify ASCII, UTF8, etc. I think the problem
with the copyright symbol is that the UTF8 converter gags on it, but
happily passes though 7-bit ASCII.  For most purposes the converter is
transparent, but it does the wrong thing for 8-bit ASCII.

Regards,
    John Labenski


On 1/22/07, John Labenski <jla...@gm...> wrote:
> On 1/22/07, Ryan Pusztai <rpu...@gm...> wrote:
> > When I wxluafreeze a script that has a Copyright symbol (c), the application
> > quits right away with no error or anything. I am using it in an about box
> > and I am just wondering if it has to do with Unicode at all. I am using the
> > prebuilt wxluafreeze from the 'bin' directory and I have built it myself as
> > well. I get the same result. Also, it works great when ran with "wxLua" and
> > not frozen. For now I am just changing the (c) to (c).
> >
> > Any thoughts would be greatly appreciated.
>
> I have tried this in the minimal.cpp sample using MS VS2005 and (c)
> does work in the about dialog there. Why it doesn't work in wxLua is
> probably because of the wx2lua and lua2wx string conversion functions
> in modules/wxlua/include/wxlstate.h.
>
> This has been discussed before, but with no resolution. The problem is
> that people make suggestions for changes to make it work for them, but
> would break things for other people. I do not understand much about
> unicode or even UTF8 strings other than a cursory knowledge so I
> cannot help much. I presented a summary of the different suggestions
> on the mailing list, but nobody seemed to know definitely what was
> right.
>
> see "wx2lua & Unicode was Re: [wxlua-users] Problem in using Turkish
> in wxLua scripts"
>
> I think we have two competing needs, unicode for international
> languages and UTF8 for ??? Can the two be mixed? I dunno.
>
> Regards,
>     John Labenski
>

Re: [wxlua-users] Unicode Problem and the Copyright symbol ((c))

[Ryan P. <rpu...@gm...>]

On 1/22/07, John Labenski <jla...@gm...> wrote:
>
> On 1/22/07, Ryan Pusztai <rpu...@gm...> wrote:
> > When I wxluafreeze a script that has a Copyright symbol (c), the
> application
> > quits right away with no error or anything. I am using it in an about
> box
> > and I am just wondering if it has to do with Unicode at all. I am using
> the
> > prebuilt wxluafreeze from the 'bin' directory and I have built it myself
> as
> > well. I get the same result. Also, it works great when ran with "wxLua"
> and
> > not frozen. For now I am just changing the (c) to (c).
> >
> > Any thoughts would be greatly appreciated.
>
> I have tried this in the minimal.cpp sample using MS VS2005 and (c)
> does work in the about dialog there. Why it doesn't work in wxLua is
> probably because of the wx2lua and lua2wx string conversion functions
> in modules/wxlua/include/wxlstate.h.
>
> This has been discussed before, but with no resolution. The problem is
> that people make suggestions for changes to make it work for them, but
> would break things for other people. I do not understand much about
> unicode or even UTF8 strings other than a cursory knowledge so I
> cannot help much. I presented a summary of the different suggestions
> on the mailing list, but nobody seemed to know definitely what was
> right.
>
> see "wx2lua & Unicode was Re: [wxlua-users] Problem in using Turkish
> in wxLua scripts"
>
> I think we have two competing needs, unicode for international
> languages and UTF8 for ??? Can the two be mixed? I dunno.
>
>
Thanks for the response, I will read the posts and see if I can offer any
insight. I am not an expert either, I just know the silent fail really is
bad and spent quite a bit of time looking for the error. Maybe just that can
be improved?
-- 
Regards,
Ryan
RJP Computing