Could the choice on font effect this ?
Also I don't understand why I get blanks instead of the string
with errors like it appears in the print out : HENW_Letebr?nner
On 8/4/2010 12:39 PM, perltk wrote:
> perl uwi_flip.pl
Well ==> HENW_Letebr?nner
> perl -C uwi_flip.pl
Well ==> HENW_Letebrønner
The output from 'perl -C' suggests to me - and I maybe wrong - that
the string is indeed unicode.
Also, the strings are displayed correctly in the Perl Tk app I am
replacing, so I think they are good.
Assuming this IS unicode - how do I correct this ??
I know very little about locale and how that effects the widgets.
Sorry about my ignorance, but Idon't understand what you are
suggesting I do :
> If the Unicode bit is not set on the scalar, the conversion from
Perl scalar to wxString should use the encoding of your current
locale, but I can't remember if if uses the system locale >or (more
likely) the locale set with wxLocale.
Thanks.
Jeff
Adding the output from perl -C says to me - and I maybe wrong - that
the string is indeed unicode.
I don't mind forcing the widgets to
On 8/4/2010 8:16 AM, Mattia Barbon wrote:
perltk wrote:
I have an app that is reading from a database. Some of the names
include unicode characters:
Heres are some print statement output when running app:
> perl uwi_flip.pl
Well ==> HENW_Letebr?nner
> perl -C uwi_flip.pl
Well ==> HENW_Letebrønner
Any names with these characters in them do not display in widgets -
they are blank.
No errors, just blank. The wxwidgets .so should be unicode.
Yes, they are.
What am I missing ?????
Are you sure that the strings you read from the database have the
Unicode flag set when read from the database? You can use the Dump()
function from Devel::Peek to check if the scalar has the Unicode bit
set.
If the Unicode bit is not set on the scalar, the conversion from
Perl scalar to wxString should use the encoding of your current
locale, but I can't remember if if uses the system locale or (more
likely) the locale set with wxLocale.
HTH,
Mattia
