1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
|
<div dir="ltr"><br><br><div class="gmail_quote">On Wed, Jul 25, 2012 at 1:56 PM, Anne Wilson <span dir="ltr"><<a href="mailto:annew@kde.org" target="_blank">annew@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<div class="im"><br>
On 25/07/12 03:23, RICHARD WALKER wrote:<br>
> On 25/07/2012, Morgan Leijström <<a href="mailto:fri@tribun.eu">fri@tribun.eu</a>> wrote:<br>
>> The system source and interface must be written in *one*<br>
>> consistent language.<br>
>><br>
><br>
> I'm not sure I understand the imperative.<br>
</div><snip><br>
<div class="im">> If I expect my users to be of many nationalities then I would also<br>
> expect to have to do some translating. The consistency of which you<br>
> speak comes from having the translations expected by the population<br>
> of users.<br>
><br>
</div>Yet surely you understand when you are told that the problem is purely<br>
a lack of manpower. Mageia would welcome en_GB translations.<br>
Register to work on it.<br>
<div class="im"><br>
>> And the fact is that the most common used language in the system<br>
>> is en_US<br>
>><br>
>> Therefor it should be purified to *en_US*<br>
>><br>
>> And all other en_* should be translations.<br>
><br>
> Again we seem to differ. I hope you didn't mean "purified", that's<br>
> probably just a mis-translation where something like "rationalised"<br>
> or "simplified" might have been a better choice.<br>
<br>
</div>No - you are wrong. "purified" means to make one consistent language.<br>
<div class="im"><br>
> Where we really differ, though, is in regarding all languages (with<br>
> the exception of the US variant of English) as being targets for<br>
> translation. I would not discriminate against our trans-atlantic<br>
> cousins in that way. I would include their language as a valid<br>
> target for translation and then we would all be equal.<br>
><br>
</div>This is utterly ridiculous. There has to be a single "core" language.<br>
That has been chosen. It is perfectly obvious that every other<br>
language must then be a translation of the core. This has nothing to<br>
do with discrimination.<br>
<br>
I am English born and bred, and 72 years old. I defend my language<br>
whenever I think it is necessary, but your stance is not defensible.<br>
<br>
<snip><br>
<div class="im">><br>
> Sensitive cultural and social use of language is much too complex<br>
> a subject for people who focus on logic to understand, especially<br>
> in a foreign language.<br>
><br>
</div>How insular can you get? No wonder the British are seen as somewhat<br>
ridiculous. Are you seriously suggesting that an Englishman cannot<br>
understand the word "color"? Of course not. Please do not waste<br>
people's time like this. If you feel strongly that there should be an<br>
en_GB translation of everything, then contribute to it.<br></blockquote><div><br>I am so glad that Anne said that, because she is one of the few people qualified to say what I, and probably several others, were thinking.<br>
I grew up learning en_US, but due to one thing or another was exposed to mainly en_GB in high school. Since I have an open mind to these things, I taught myself en_GB spelling, grammar (which is slightly different when spoken) and idioms. Of course I am most comfortable in en_US, but that's not the point. The point is the mindset. This stubbornness of "how darest thou dilute my native language with the vulgarities of another" is very off-putting. In fact, it makes me instinctively want to retaliate in kind, and quickly degrade to name-calling and pinching. It indicates that this person does not really want to formulate any kind of change or anything. No, they just want to complain. And loudly.<br>
Rather than jump on a soap box and pontificate to a mostly indifferent audience, why not do something about it?<br>We have all been saying over and over again that this was not done out of malice, callousness or some perverted desire to errode the British language. It was done this way to conform with well-established standards and common practice. The only thing preventing drakx tools from having certain British spellings is a lack of manpower.<br>
Anybody and everybody is welcome to provide input, criticism and their own opinion. But what makes it constructive criticism is the way it is delivered, and what you are willing to do about it.<br>As they say in NY, put out or get out. The British translation for that would be: get down from your high horse and help out or just go away.<br>
So please, you are welcome to join the Mageia team and provide an en_GB translation for what is missing. You are welcome to sit in silent defiance and nurse your stubbornness. But this, this angst-driven tirade? This is not welcome at all. It only generates more angst.<br>
</div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Anne<br>
- --<br>
Need KDE help? Try<br>
<a href="http://userbase.kde.org" target="_blank">http://userbase.kde.org</a> or<br>
<a href="http://forum.kde.org" target="_blank">http://forum.kde.org</a><br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.12 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
<br>
iEYEARECAAYFAlAP0L4ACgkQj93fyh4cnBfC+wCfZEeg2Qf/hASq9aeyXPdWUo/c<br>
LSUAn3h+3Ging0aW3TFQQXongYNoZiDa<br>
=hLmO<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br></div>
|
