1 |
Hi, |
2 |
|
3 |
|
4 |
Patrick Lauer <patrick <at> gentoo.org> writes: |
5 |
> |
6 |
> Enabling the unicode useflag in the profiles should help our |
7 |
> international users and should not cause any problems. [...] |
8 |
> |
9 |
> On a tangent I wonder if pulling in extra fonts as a dependency of X |
10 |
> makes sense (useflag controlled, enabled by default) - that way the |
11 |
> unicode capabilities are available without any configuration. |
12 |
> |
13 |
|
14 |
|
15 |
Don't forget about the kernel configuration, the locales configuration, and |
16 |
individual apps configuration (run-time configuration, I mean). |
17 |
|
18 |
See: http://www.gentoo.org/doc/en/utf-8.xml |
19 |
|
20 |
Having all this done automatically would indeed be nice. |
21 |
|
22 |
|
23 |
> |
24 |
> Are there any known bugs / problems this would trigger? Any |
25 |
> reasons against that? |
26 |
> |
27 |
|
28 |
|
29 |
The classic problem is that non-ASCII characters will not be readable by the |
30 |
people still not using UTF-8, instead of their old ISO/other charset... |
31 |
|
32 |
If someone is using an old ISO/other charset and someone else is using UTF-8, |
33 |
and if they speak the same language, they won't be able to understand |
34 |
eachother's non-ASCII characters... (and most users won't understand why -and |
35 |
most users will blame it on the configuration of the user using UTF-8 :/) |
36 |
|
37 |
Classic case of incompatibility hell... |
38 |
|
39 |
UTF-8 is here to solve this, but it only works if everybody changes to UTF-8... |
40 |
but as long as not all software support UTF-8 (sometimes, they don't, only |
41 |
because the devs don't feel like it is necessary :/), and as long as not every |
42 |
users use UTF-8, then it will be perfectly respectable to stick to ISO/other |
43 |
charsets, to avoid problems with family members, friends and colleagues who |
44 |
still use ISO/other charsets and don't want to change or just can't change... |
45 |
(Windows users, mostly). (This is pretty similar to the situation concerning |
46 |
instant messaging... you want to go to Jabber, but everyone else is using MSN, |
47 |
AIM, ICQ and Yahoo...). |
48 |
|
49 |
This is why we should still not go with fully activating UTF-8 as default... |
50 |
what we should do, is ease the migration to UTF-8, for everyone who feel like |
51 |
using it... (and for everyone whose family members, friends and colleagues |
52 |
already use UTF-8 -but it should be quite rare). If it's easy, more and more |
53 |
people will migrate, and when Windows will activate UTF-8 by default (let's pray |
54 |
MS will feel like implementing this correctly), and most Windows users have |
55 |
updated (or went to Linux/BSD/other ^_^), then we should switch to all UTF-8 by |
56 |
default. |
57 |
|
58 |
Until then, as said, the migration should be easier for the user... it means we |
59 |
should also take care of run-time configuration, maybe with a new USE flag, to |
60 |
preconfigure every programs which support UTF-8, to use it by default (instead |
61 |
of just supporting UTF-8, with the "unicode" USE-flag). Of course, the kernel |
62 |
and locales should also be configured automatically. |
63 |
|
64 |
Then, another great thing would be to be able to easily press the backpedal and |
65 |
goes back to ISO/old charset, if too many incompatibility problems arise... (if |
66 |
it's hard to come back, and they have problems, people will hate UTF-8 for years |
67 |
:/ -and they'll tell other). |
68 |
|
69 |
Instead of an USE-flag for default preconfiguration, maybe a script could take |
70 |
care of modifying the user programs configuration, to easily activate and |
71 |
deactivate UTF-8 by default, in every supported programs... (well, the script |
72 |
would also allow to configure programs one at a time). |
73 |
|
74 |
We should also grealty document the migration process and the incompatibility |
75 |
problems which may arise if you try to communicate with people using ISO/old |
76 |
charsets... (and grealty explain them the use of `iconv` and similar programs). |
77 |
|
78 |
Another thing is to list every packages which do not support UTF-8... (editors, |
79 |
like NEdit, for example), and maybe make `emerge` warn the user, if he uses |
80 |
UTF-8, that the package he is trying to emerge, do not support UTF-8... (well, |
81 |
an ewarn, at the end of the emerging process would be enough, but to be warned |
82 |
before emerging the package would be nice). |
83 |
|
84 |
Anyway, we should separate "activating support for Unicode/UTF-8" and |
85 |
"activating use of UTF-8, by default, in every programs", and we should support |
86 |
both... |
87 |
|
88 |
If they can be cleanly be separated, we should probably activate support for |
89 |
Unicode/UTF-8 by default, now... but as said, activating use of UTF-8 by default |
90 |
for all program should not be done until quite some time... |
91 |
|
92 |
|
93 |
Cya. |
94 |
|
95 |
|
96 |
-- |
97 |
gentoo-dev@g.o mailing list |