Text Encoding for Filename is not uniform in wxMac-2.6.3
Stefan Csomor
csomor at advancedconcepts.ch
Wed Aug 2 05:13:51 PDT 2006
Hi
we've had a difficult decision where to draw the line.
The current thinking is that any call that takes char* should get utf8
decomposed (ie use fn_str() et al by the caller), any call with wxString
param, should have the ui encoding.
I've added conversions for utf8 composing / decomposing in CVS HEAD, so
this one should be better for testing. Once we've ironed out the
wrinkles, I'll backport if possible to 2.6.X
Best,
Stefan
> -----Original Message-----
> From: BawaSingh [mailto:bsingh at rebaca.com]
> Sent: Mittwoch, 2. August 2006 14:15
> To: wx-users at lists.wxwidgets.org
> Subject: Text Encoding for Filename is not uniform in wxMac-2.6.3
>
> I am using wxMac-2.6.3 on Mac OS 10.3.9 Xcode as IDE and gcc
> 3.3 as compiler.
> I am facing one problem, when my program deals with the
> file/dir names having special characters, some functions like
> wxFileExists expects the filename in Default Mac System
> Encoding (MacRoman) format while wxDirExists demands in UTF8
> Decomposed.
> Does it means the implementation is not uniformaly distributed.
>
> Is this a bug in wxMac-2.6.3 or is there something wrong in my
> wxMac-2.6.3 build.
> My program was doing very well with earlier wxMac-2.5 Library.
> wxMac-2.5 was taking the file/dir names in UTF8 Decomposed throughout.
>
> Is this issue with wxWidgets-2.6.3..?
>
>
> Thanks
> Bawa Singh
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wx-users-unsubscribe at lists.wxwidgets.org
> For additional commands, e-mail: wx-users-help at lists.wxwidgets.org
>
>
More information about the wx-users
mailing list