Re: wxString and UTF-8, utf8 etc etc etc again

2013-05-02 Thread Johan Vromans
Mark Dootson mark.doot...@znix.com writes: None of my machines can be ASCII or EBCDIC by whatever definition this doc entry uses [...] What exactly is an ASCII machine? ASCII just means: non-EBCDIC. Anyhow, I find that after $string = decode(utf8, $octets) $string always has the utf8

Re: wxString and UTF-8, utf8 etc etc etc again

2013-05-02 Thread Mark Dootson
Hi, On 02/05/2013 10:34, Johan Vromans wrote: The question is: do we consider wxWidgets to be 'external world'. That answer is most likely 'yes'. But more important: do we consider wxPerl to be 'external world'? I'd say 'no'. Therefore, what I'd expect to pass to a wxPerl routine is a string

RE: wxString and UTF-8, utf8 etc etc etc again

2013-05-01 Thread Steve Cookson
Hi Guys, I don't have anything broken in this release in the 2 languages that I currently support (English and Portuguese). But even so, the whole utf8 process has been a bit time consuming. As we become more multilingual, I'm thinking that a global change to rename decode to libDecode (or

Re: wxString and UTF-8, utf8 etc etc etc again

2013-05-01 Thread Mark Dootson
Hi, On 02/05/2013 00:17, Steve Cookson wrote: Or just sub libDecode ($$){ return decode(@_); } At least all the things that might go wrong will all be here. You're unduly worried ( probably my fault ). my $string = decode($encoding, $binary); Is fine. Cheers Mark

Re: wxString and UTF-8, utf8 etc etc etc again

2013-05-01 Thread Octavian Rasnita
From: Mark Dootson mark.doot...@znix.com Hi, On 02/05/2013 00:17, Steve Cookson wrote: Or just sub libDecode ($$){ return decode(@_); } At least all the things that might go wrong will all be here. You're unduly worried ( probably my fault ). my $string = decode($encoding,