Alastair Tse kirjutas N, 30.10.2003 kell 18:08: > On Thu, 2003-10-30 at 11:44, Mamoru KOMACHI wrote: > > > > /me votes for unicode use-flag > > > > > > should also be activated in all profiles by default. > > > > Any objection if I add unicode USE flag (and make it default in all > > profiles) ? We cannot simply convert cjk USE flag to unicode, but in > > wxGTK is currently using a local unicode useflag to enable unicode > support. However, this is experimental so I rather not have unicode > default in all profiles just yet. By compiling with the unicode useflag, > you'll end up with certain wxGTK apps failing to merge.
Sorry for a really delayed answer. To my knowledge unicode support in wxGTK isn't experimental but rather suggested but not enforced. The reason why certain wxGTK apps fail to merge is that they don't comform with the unicode wxWindows prerequisites. Quote from wxWindows docs: "The important conclusion is that if you use wxChar instead of char, avoid using C style strings and use wxString instead and don't forget to enclose all string literals inside wxT() macro, your program automatically becomes (almost) Unicode compliant!" Those certain apps fail to follow the above. And to be honest, my own wxWindows projects fail to follow it aswell, but that will be fixed soon ;) Oh, and instead of wxT() one should use _() to automagically add i18n support aswell. So my conclusion is that we still should make USE=unicode be default (put into the profiles), but ebuilds that depend upon wxGTK should be checked if the wxWindows app is unicode aware or not. If it isn't then it should simply remove the unicode flag in the ebuild. Personally I would add the unicode flag to make.conf and wxGTK apps that don't compile emerge with USE=-unicode, also I'd prod the app devs to make it follow wxWindows unicode prerequisites that aren't hard to follow (personal experience). -- [EMAIL PROTECTED] mailing list
