Archives/2007-03-23
From LangCom
![]() |
This page is no longer maintained and may be outdated: moved to m:Special projects subcommittees/Languages/Archives/2007-03-23. |
Archived discussion |
This is an ongoing email discussion about the Kabyle Wikipedia and localization. |
1. |
Jesse Martin (Pathoschild) Hello, I propose the subcommittee approval of the Kabyle Wikipedia. This language is well-established, has a very wide audience, a large interested community, a unanimous discussion on Meta, and a standard code. In addition, the test project is very successful with over 200 pages and daily activity by multiple users. Although the project is not localized due to the technical difficulty of localizing without a wiki, the community is more than strong enough to localize with Special:Allmessages once the wiki is set up; there's no reason they would use an English interface. This translation can be added to the localization files by the time a second Kabyle project is approved. This opinion was seconded by Aphaia, member of the translation subcommittee.
Yours cordially, |
2. |
Berto 'd Sera Hoi! > the technical difficulty Pls explain. What's more difficult for them in respect to any other linguistic entity? Why can’t they use Betawiki? I'm quite against making *any* exception whatsoever. If we allow a wiki without localization (no matter which one and why) we either allow them all or promote the idea that LangCom makes arbitrary decisions based on personal sympathy and internal mafia. We may mean good but that's the way anyone would interpret such a move. We just canceled all pending applications and keep on hold tens of requests because they miss a localization file, make 1 + 1 and you'll have the meaning that the community will attribute to any single exception... Do we need that? Bèrto ‘d Sèra |
3. |
Jesse Martin (Pathoschild) Hello, There is no exception to make; we never agreed to localization as a prerequisite and it is not part of the policy. BetaWiki is complex to edit and is not affiliated with the Wikimedia Foundation. This method requires that editors register to a third wiki (Meta, Incubator, and Beta-Wiki), explicitly define required preferences, acquire special permission to translate the interface (the "translator group"), and learn to use the translation interface. Every translator must do this; since the only instructions for this complex procedure are in English, bilingual users will need to translate the instructions to the relevant language for those who aren't. Furthermore, users cannot translate important wiki-based pages such as the sidebar. On the other hand, translating live consists of going to "Special:Allmessages", clicking a redlink, and filling in the translation. If BetaWiki were merged into the Incubator as an extension, it would be much more workable; users could translate the entire wiki simultaneously. However, it is not very workable as a separate, unaffiliated, complex procedure on a personal test wiki. Yours cordially, |
4. |
Berto 'd Sera Hoi! Okay, let's try and see some light in the tunnel :) 1) I maintain PMS in betawiki myself and made its first interface by editing AllMessages myself, single-handed. It takes but a couple of days in all. BTW, I use a 16kbits dialup on a very aged soviet telephone line. You don't need a broadband connection to use goodwill and there's nothing complex in reading an expression and writing an equivalent in your native language. If even the translator cannot understand an expression, then HOW do we expect a not bilingual community to be able to use it?????????? In short, I officially oppose the creation of ANY unlocalized wiki. You can record this opposition vote as unchangeable for any further such request. Bèrto ‘d Sèra |
5. |
Jesse Martin (Pathoschild) Hello, As far as I can tell, none of the policy drafts at <http://langcom.wikimedia.org/wiki/Language_proposal_policy> have ever required localization. What do the other subcommittee members think of requiring full localization before approval? Yours cordially, |
6. |
Berto 'd Sera Hoi again, Jesse , pls don't take my position as a personal will to blunt lock-gates against any new project. As a matter of fact I'm spending a huge number of hours in translating wikipedia articles in rare slavic languages that are full of political assertions that (if translated and published) would *seriously* damage our public image. You don't want donors to know that their donations are used to publish revisionist history, a blatant usage of terms that equivalent to *nigger* in their racial derogatory value, etc, etc. So what many of us do is keeping a monitoring eye on as many languages as possible and eventually get to the point in which some Committee will decide of the most dangerous events. It's quite true that having a real community is not a warranty about the neutrality of a wiki, yet as a matter of fact most of the weirdest wikies happen to be managed by a couple of overheated extremists. Maybe if we had a required a wider number of users for a starting edition this problem would have been reduced. If we want users to take wikipedia seriously we must not make a toy of it since the very start. I'm positive you just want to help people, yet there is no good thing in life that one can get for free. Valuable things always come from hard work and a good wiki is no exception. Bèrto ‘d Sèra |
7. |
Jesse Martin (Pathoschild) Hello, Did you mean to send that last message to the whole subcommittee or only to me? I agree with what you're saying; those are the problems I wanted to prevent when I wrote the policy draft a few months ago, and it is one of the reasons we require a successful test project before approval. However, I don't think localization of the interface itself before approval rather than after will affect the viability of the communities or the veracity of the content. Yours cordially, |
8. |
Berto 'd Sera Hoi! Yes, it was for all. I'm getting sleepy (8.35 am on the eastern front) and I simply landed on the wrong button :) I wrote a number of things about localization for small communities here: http://eng.i-iter.org/making-new-semantic-domain As a matter of fact making a wiki interface is "inventing a semantic domain". That cannot be done by a lot of concurrent hands because it will result into a unusable jam. A community should really choose one or more interface editors and it should discuss about the language they "create". Being immediately understandable to a native speaker who never really used technology is 90% of the marketing behind a small language wiki. We had our first 5 nation-wide press articles just because our literal translation of the term WEB sounded funny (actually I just picked it up from a friend as I found it funny, too). Our term "Ragnà" (web) prompted the first printed appearance of text in the piemontese language on the national press in 150 years, because then they moved to discuss our GNU license, etc etc. We keep having press coverage mainly because the italian local languages do translate those english words that the italian interface imported as unchanged. It's not just a small procedural step we talk about, interface language is a big asset for a wiki, maybe the biggest asset a wiki can have because it defines how usable (or cryptic) that wiki will be. Bèrto ‘d Sèra |
9. | |
10. |
Sabine Cretella Hi, I just came back home: well localization is the basics ... and for Neapolitan I still have a hard time to get people to localize stuff in the right place: so new projects should avoid these problem in a first place. If they learn to maintain the localization directly on betawiki from the beginning they will always do it - if you allow for anything else ... you get projects that even after half a year are not localized. See the so-called Tarantino wikipedia: http://roa-tara.wikipedia.org/wiki/Pagene_Prengep%C3%A1le If they have time to write the articles they should also have time to do the localization ... or am I wrong? Having the localization done before a wiki is opened was always the goal. Sorry for being short - have to put things away. Ciao, Sabine |
11. |
Jesse Martin (Pathoschild) Hello, There seems to be a consensus in favour of requiring localization, so I'll accept it. I've implemented it as a requirement in the language proposal policy. I thus propose the following procedure to streamline and simplify the Kabyle localization. This will be a good test case for future localization efforts.
What do you think of this process? Yours cordially, |
12. |
Jon Harald Søby) Well, after reading the slaughtering thread, I think there are some good arguments against demanding a localisation beforehand. Localisation is very hard work, and even I, who have been involved with wikis for more than two years now, in a lot of ways (as common user, anon, sysop, steward, bot operator), don't even know what some of the messages in "core" on BetaWiki actually mean, and have never encountered them. What I suggest is that we make a list of the real core messages, perhaps around a hundred of them or so. What I suggest is that the main page, and all pages linked from it in the menus, etc, are to appear fully translated to begin with. Then, when they start the Wikipedia, they can translate the rest, if they feel like it. But it shouldn't be a requirement to have everything translated. (Not even Norwegian, which has more than 100 000 articles, have a fully translated MediaWiki message system; most of what's untranslated are those stupid and pointless Exif- messages, though, while the rest is translated.) -- Jon Harald Søby |
13. | |
14. |
Jesse Martin (Pathoschild) Hello GerardM, I proposed the selection of a small number of editors based on the advice of Bèrto 'd Sèra earlier in this discussion: "As a matter of fact making a wiki interface is "inventing a semantic domain". That cannot be done by a lot of concurrent hands because it will result into a unusable jam. A community should really choose one or more interface editors and it should discuss about the language they "create"." Do you disagree with this advice? Yours cordially, Jesse Martin (Pathoschild) |
15. |
Berto 'd Sera <this block of text is marked as private.> EXIF msgs... they are pure bullshit, I'm lucky me and my dad have always played with cameras, but I really hated them when I translated them :)))) I'm also positive 100% translations can't be made (new messages appear/get changed almost every day). It's one more reason to have someone keeping a constant eye on the UI. At least all commands should be translated (and the copyright statement, too, because it's a contract and end-users have the right to understand what they implicitly sign), but whether you translate EXIF msgs or the like of it IMHO is largely a matter of choice. This should be a process by which a community "configures" its own wiki and learns how a wiki works and what admins are supposed to do with it. My best option would be an incubator mailing-list, in which translators and would-be admins could get to know each other and help each other. Anyway... what if we stop talking theory and we start an experiment? We can use it to document the process and later make adjustments while we learn from a case of study. Let's begin this Kabyle translation, so we can address real problems as they come. Bèrto ‘d Sèra |
16. |
Jesse Martin (Pathoschild) Hello, I agree; localizing every last message is unnecessary. Perhaps we should determine the files to be localized in discussion with the Kabyle community; this collaboration will simplify the process for us, improve the accuracy and quality of our selection, and the involvement of the waiting community will alleviate impatience. GerardM has stated that all users should translate the interface simultaneously; Berto has stated that they should select a few users to work on the interface. I prefer the latter, as I proposed above. Any other opinions? Are there any objections otherwise to my above proposal (contact the users, centralize discussion and collaboration)? Yours cordially, |
17. | |
18. |
Berto 'd Sera
|
19. | |
20. | |
21. | |
22. |
Jesse Martin (Pathoschild) Hello, There doesn't seem to be any opposition to centralizing discussion at <http://meta.wikimedia.org/wiki/Talk:Requests_for_new_languages/Wikipedia_Kabyle>. This is a pretty logical choice, so there's no need to nominate or vote on it, nor establish any codified procedure. I don't oppose a free-for-all localization; this will be a good chance for the users to get to work together, and mistakes can easily be corrected by other editors. Berto, do you oppose this? There doesn't seem to be any support for assigning subcommittee members to help, so I'll just make sure to watch the discussion to make sure all their questions are answered. If there's no opposition to a loose collaborative method (centralized discussion, free-for-all localization), I will announce that and get it going as soon as possible. Yours cordially, |
23. | |
24. | |
25. |
Jesse Martin (Pathoschild) Hello, Alright then. If there's no opposition to the adjusted proposal, we'll begin tomorrow. This isn't a codified procedure, just a way we can proceed with the Kabyle Wikipedia. 1. Set up the request discussion page to answer questions, provide updates, and coordinate localization. 2. Contact every user who has expressed an interest in contributing of this effort. 3. Help any interested user begin localizing. Yours cordially, |
26. |
Berto 'd Sera Hoi! Okay for me, I would add a sort "contact structure". I mean, we speak different languages, I just started correspondence with the Ingush because we have a common russian, maybe there are other people who can volunteer their languages with other fallbacks. The further we get from the West the more important it will be to be able to deliver assistance in non-english form. Bèrto ‘d Sèra |
27. |
Jesse Martin (Pathoschild) Hello, With no opposition, I've started the localization process and mentioned it in the relevant mailing list discussion.
Yours cordially, |