Joel Spolsky's Translations Wiki
Joel Spolsky, author of the very popular technical blog Joel On Software, is currently doing an experiment of using a wiki for translating his blog content into other languages. From his global readership, Joel definitely has the resources to do the translation, it was just the management and coordination that proved to be the problem:
Sadly, I fell down in face of the effort needed to maintain 30-odd local language versions. Such a job can’t be coordinated by one person, especially when that person is me.
The translation wiki (powered by MediaWiki) seems to be having some success. Joel announced the wiki on January 27th and there are already 117 registered users generating a good amount of content. The Spanish, Greek, Hebrew, Japanese, Polish, and Russian sections have the most translations.
A wiki allows users to work directly with each other to sort out issues like “speakers of the Flemish dialect ask me to change it one way, then speakers of Netherlands Dutch suggest putting it back, and I have no idea what they’re talking about!” What of the concern of vandalism? Joel feels confident that the community will work it out: “If you’re feeling naughty, add some fart jokes to somebody’s excellent translation. We’ll see if the community spots it and fixes it.” Fortunately, the Joel’s readership is probably dedicated and smart enough to be up to the task. (BTW, there are two very good articles on Wikipedia in the Boston Globe here and here that talk about the culture of the Wikipedia). There is also a page that serves a place to discuss cultural reference and terminology questions. There is also a kind of logistics page and a guidlines page to mention best practices.
So what are the weaknesses of this format? The key one that I see is the lack of structure. However, it is really no worse than the source (blog entries) the only thing missing is a field for date and title. There is a guideline to link back to the source article so it may be possible for the translations to share this information with the original article through a very loose foreign key relationship. Using WikiText may make it easier to parse content than giving users HTML WYSIWYG editors. It is not too difficult to parse MediaWiki text. For example, “==” means a HTML heading level two (H2) tag. But in a WYSIWYG editor, you would most likely get some kind of font tag which would give you no clue that this was the heading of a section.
I will keep my eye on the Joel on Software translation wiki. It looks like it has all the ingredients for successful wiki: dedicated readership, good content, and community.