Gentoo Archives: gentoo-project

From: "Paweł Hajdan
To: gentoo-project@l.g.o
Subject: Re: [gentoo-project] wiki: bad top-down localization approach
Date: Wed, 26 Oct 2011 07:29:06
Message-Id: 4EA7B69B.70904@gentoo.org
In Reply to: Re: [gentoo-project] wiki: bad top-down localization approach by Peter Volkov
1 On 10/19/11 9:34 PM, Peter Volkov wrote:
2 > Funny ... those who are most interested in having language-specific
3 > pages are unable to take part in our discussion due to language
4 > limitations ;) But still they ping me in IRC/xmpp so partially they
5 > pushed me onto this topic.
6 >
7 > В Срд, 19/10/2011 в 15:43 +0200, "Paweł Hajdan, Jr." пишет:
8 >> On 10/19/11 3:31 PM, Christian Ruppert wrote:
9 >>>> Hello. While it is not tool late, could you guys reconsider top-down
10 >>>> localization approach decided on last meeting[1]?
11 >>>>
12 >>>> There are language specific things that will be be kept out of wiki
13 >>>> only due to this policy. For example I don't see any reason to write
14 >>>> article about use of Russian cryptography algorithms in Gentoo in any
15 >>>> language but Russian. There is no need to have this article in
16 >>>> English since nobody will read it.
17 >>
18 >> Maybe those rare cases can just use the unofficial wiki? It seems to me
19 >> that it would support that scenario.
20 >
21 > Why?
22
23 Why I think the unofficial wiki would support the scenario? I don't
24 know, this was just a guess, but I think someone wrote in the thread
25 that it would.
26
27 Why do I think people who want to write say Russian-only articles should
28 use the unofficial wiki?
29
30 1. Because they can, and it works, and official wiki at least initially
31 wouldn't.
32
33 2. Then you have something, and you can move this over to official wiki
34 later when it supports it. It's easier to convince people to start
35 supporting this when you have an existing high quality set of articles.
36
37 > Well, I don't have statistics for now and I can start poll on gentoo.ru
38 > to get back with results, but my guess is that about 90% of Russian
39 > community users are unable to write English documentation. Still there
40 > are active users who share their solutions fixes/ideas.
41
42 That's good,
43
44 > Last week my co-worker installed Gentoo based on "misleading and
45 > partially wrong" but still Russian only documents. He is practically
46 > unable to read English well but uses Ubuntu for many years and now I've
47 > forced him to use Gentoo (Yay! :) ) Also he programs php and yet there
48 > are lots of technical books in Russian.
49
50 Why don't we have an official Russian translation of the Handbook then?
51 IMHO it's even more important than having Russian-only articles on
52 not-yet-existing official wiki.
53
54 >> I think for non-technical users it can make a difference.
55 >
56 > I think vice versa. In technical literature the number of words is very
57 > limited so it's possible to learn some basic words and be able
58 > understand a "general" idea of the document. Code examples or listings
59 > helps here very much. But this "understanding" is not the same as
60 > writing English. Reading != writing.
61
62 Right, good point.
63
64 >>> We also use English for our Mailinglists, IRC, Forums, Bugzilla and so
65 >>> on, why? Because everybody can read it.
66 >>
67 >> Yeah.
68 >
69 > Bad example since there are Russian mailing lists, IRC, forums and users
70 > requested me many times to create Russian bugzilla :)
71
72 Nobody prevents anyone from creating an unofficial one, but I'm not
73 going to fix bugs reported to it. ;-)
74
75 >>> Another *bad* example are translated error messages.
76 >>> Do you like to get bug reports with German error logs?
77 >>
78 >> +1
79 >
80 > np here. If error message is unreadable I just request additional
81 > information.
82
83 That introduces some delays, and sometimes reporters fail to post the
84 requested info. It's generally much easier if you get the right thing
85 from the start.
86
87 > That said I see that you already set on this. Well... Let's see how it
88 > goes in real life but it'll be great if there will be no such
89 > requirement "hardcoded". It'll be cool if you provide mechanism to allow
90 > easy extension for language specific pages in future.
91
92 My understanding is that it could possibly be changed in the future.

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies