{"id":422,"date":"2006-08-09T09:07:10","date_gmt":"2006-08-09T14:07:10","guid":{"rendered":"http:\/\/www.bytebot.net\/blog\/archives\/2006\/08\/09\/community-contributed-documentation-tamil-sees-some"},"modified":"2006-08-09T09:07:21","modified_gmt":"2006-08-09T14:07:21","slug":"community-contributed-documentation-tamil-sees-some","status":"publish","type":"post","link":"http:\/\/www.bytebot.net\/blog\/archives\/2006\/08\/09\/community-contributed-documentation-tamil-sees-some","title":{"rendered":"Community Contributed Documentation – Tamil sees some"},"content":{"rendered":"

Open source projects have a lot of documentation. Some professionally written<\/a>, others community contributed<\/a>. One thing that community contributed documentation has going for it is the passionate users that write localized content<\/strong>.<\/p>\n

Localization of documentation is important. While we take it for granted that we all speak\/read\/write\/understand the English language, a lot of people just starting out in non-English speaking areas might find it useful to read some localized content. Hook them based on their interests, and slowly they can be weaned off to other non-localized documentation, and might contribute to the localizing cause eventually, even.<\/p>\n

Localization is also not easy. If you tried to localize the MySQL Documentation<\/a>, its recommended you start with something smaller like the GUI tools, rather than the entire user manual. This because of its sheer size. I dare say, we have one of the best user manuals for any open source project out there. Its cogent, its concise.<\/p>\n

Tamil (Indian) Documentation<\/strong>
\nBut the point of this post, was really to encourage more community contributed documentation. Of late, we’ve had some Tamil<\/a> documentation, that I myself can’t review, but I’m sure the collaborative and distributed nature of the Internet will enable us to find some Tamil reading people, who can write better, and longer descriptions about what’s there.<\/p>\n

I’m sorry its a Word document. I didn’t want to convert it to a PDF because I have no idea if the fonts will break. For what it is worth, there is a supplied font<\/a> that you might find useful, if you were reading it. Now, who wants to review<\/em> it?<\/p>\n

Blogs via Planet MySQL<\/strong>
\nIf you read Planet MySQL<\/a>, you’ll realize that quite a lot of the content there is high-quality MySQL related content. What you will also realize is that these are on individual user blogs, and its all fed based on topic and regex searches (thanks Arjen, for this!). But content within Planet MySQL disappears from the front of the page after 10 entries. <\/p>\n

To fix this, there are the Planet MySQL Archives<\/a>. If you notice, these are actually cached on Planet MySQL itself, so the content will be preserved if you move blog host, or somehow manage to be taken off the Internet. However, this isn’t a hundred percent solution, as not all the content on the Planet are actually “article material”<\/em>.<\/p>\n

So wouldn’t it be nice if all the article material<\/em> were on the MySQL Forge Wiki<\/a>? This way, we would have a community-based data store, with available information for all to draw on. <\/p>\n

What are your thoughts? Is publishing on the wiki too difficult? I’m interested in hearing your comments (or even better, tell me what your blog posting workflow is like). colin AT mysql dot com<\/em> works too.<\/p>\n

Share this:<\/h3>