1 |
Alastair Tse kirjutas N, 30.10.2003 kell 18:08: |
2 |
> On Thu, 2003-10-30 at 11:44, Mamoru KOMACHI wrote: |
3 |
> > > > /me votes for unicode use-flag |
4 |
> > > |
5 |
> > > should also be activated in all profiles by default. |
6 |
> > |
7 |
> > Any objection if I add unicode USE flag (and make it default in all |
8 |
> > profiles) ? We cannot simply convert cjk USE flag to unicode, but in |
9 |
> |
10 |
> wxGTK is currently using a local unicode useflag to enable unicode |
11 |
> support. However, this is experimental so I rather not have unicode |
12 |
> default in all profiles just yet. By compiling with the unicode useflag, |
13 |
> you'll end up with certain wxGTK apps failing to merge. |
14 |
|
15 |
Sorry for a really delayed answer. |
16 |
To my knowledge unicode support in wxGTK isn't experimental but rather |
17 |
suggested but not enforced. |
18 |
The reason why certain wxGTK apps fail to merge is that they don't |
19 |
comform with the unicode wxWindows prerequisites. |
20 |
Quote from wxWindows docs: |
21 |
|
22 |
"The important conclusion is that if you use wxChar instead of char, |
23 |
avoid using C style strings and use wxString instead and don't forget to |
24 |
enclose all string literals inside wxT() macro, your program |
25 |
automatically becomes (almost) Unicode compliant!" |
26 |
|
27 |
Those certain apps fail to follow the above. And to be honest, my own |
28 |
wxWindows projects fail to follow it aswell, but that will be fixed soon |
29 |
;) |
30 |
Oh, and instead of wxT() one should use _() to automagically add i18n |
31 |
support aswell. |
32 |
|
33 |
So my conclusion is that we still should make USE=unicode be default |
34 |
(put into the profiles), but ebuilds that depend upon wxGTK should be |
35 |
checked if the wxWindows app is unicode aware or not. If it isn't then |
36 |
it should simply remove the unicode flag in the ebuild. Personally I |
37 |
would add the unicode flag to make.conf and wxGTK apps that don't |
38 |
compile emerge with USE=-unicode, also I'd prod the app devs to make it |
39 |
follow wxWindows unicode prerequisites that aren't hard to follow |
40 |
(personal experience). |
41 |
|
42 |
|
43 |
-- |
44 |
gentoo-dev@g.o mailing list |