Bug #44033 | Is there any way to submit a new language for error messages to you? | ||
---|---|---|---|
Submitted: | 2 Apr 2009 6:45 | Modified: | 12 Aug 2010 7:38 |
Reporter: | shanyan baishui (OCA) | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Errors | Severity: | S4 (Feature request) |
Version: | ALL | OS: | Any |
Assigned to: | Assigned Account | CPU Architecture: | Any |
Tags: | Contribution |
[2 Apr 2009 6:45]
shanyan baishui
[2 Apr 2009 8:16]
Susanne Ebrecht
Many thanks for writing a feature request. We are not prepared for it at the moment. Anyway I will give this to development to let them know about your offer.
[8 Apr 2009 6:05]
Alexander Barkov
Hello shanyan, thank you very much for your contribution into MySQL! Which language would you like to contribute? Can you please attach the new file into this report for review?
[8 Apr 2009 9:43]
shanyan baishui
some chinese simplified error message translation demo
Attachment: errmsg-5.1.33-chinese-simplified.txt (text/plain), 6.10 KiB.
[8 Apr 2009 10:06]
shanyan baishui
Hi Alexander, i just upload the translation demo. as you can see that is a chinese(simp) translation. i don't know how to edit sql/share/errmsg.txt and keep all characters correct easily (they have different charsets, maybe there have some editor can do this, but not very easy), so i picked "eng"s up and added my translations. this translation is based on mysql 5.1.33, and the encoding is gbk, also gb2312 is ok. thanks for pay attention to us, i will continue on work of translations(such as phpMyAdmin, you can see our work in phpMyAdmin develop SVN, it was finished, but new language string added), also a friend of me, but not 24h, i have my own job, and he ... busy now, so it may little slow. regards
[8 Apr 2009 10:53]
Alexander Barkov
Hi shanyan! Thank you very much! The file looks fine. We can merge your file into the main file later, so it's Ok just to create a file with English and Chinese languages, to make it edit easier. Which version is this file for? I recommend to use 6.0 as the base. Thanks!
[8 Apr 2009 11:14]
shanyan baishui
Hi Alexander! Very glad to we can do something for MySQL! that file was based 5.1.33, but don't worry, i will work on both 5.1.33 and 6.0. when translation finished, i just need upload files to here right?
[8 Apr 2009 11:32]
Alexander Barkov
Yes, please attach the new versions here so far. Meanwhile I'm getting in touch with our Contributed Work Coordinators. I'll let you know if they give me some other instructions. Thank you!
[14 Apr 2009 13:01]
shanyan baishui
chinese simplified error message translations
Attachment: errmsg-chinese-simplified-translations.zip (application/zip, text), 125.42 KiB.
[14 Apr 2009 13:02]
shanyan baishui
Hi Alexander, i was just finished the translation, see attach pls.
[14 Apr 2009 13:09]
Alexander Barkov
Hi Shanyan! Excellent! Thank you very much for your contribution. There's one thing left before we can include it into the MySQL source tree, you need to sign the Sun Contributor Agreement (SCA). Can you please have a look here: http://forge.mysql.com/wiki/Contributing_Code#Paperwork Thanks!
[16 Apr 2009 12:23]
shanyan baishui
Excuse me, Alexander, did you receive the message that i sent to you for some questions about SCA yesterday?
[16 Apr 2009 12:37]
Alexander Barkov
Hi Shanyan, Everything looks correct. The language doesn't matter. Chinese or Chinese PinYin - either of them will do. English will do as well. Thanks!
[2 May 2009 3:13]
shanyan baishui
Hi, Alexander! my SCA has been approved and you can find me "Shanyan Baishui" in the "B" section https://sca.dev.java.net/CA_signatories.htm#b Thanks!
[4 May 2009 11:52]
Alexander Barkov
Hi Shanyan! Thank you very much for signing the SCA! We're looking for Chinese speaking reviewers for your contribution at the moment. After review is done, the contribution will go inti an official mysql release, most likely mysql-5.4. I'll keep you informed.
[5 May 2009 6:52]
Zhenxing He
I will review the translation, and I hope that I can finish it this week (before May 8)
[11 May 2009 13:22]
Zhenxing He
Hi shanyan, baishui Thanks for your valuable work and contribution, and sorry for delay of the review, I have just finished the first review of the translation, I'll re-check it and add my comments here soon tomorrow.
[12 May 2009 9:27]
Zhenxing He
comments on the translation
Attachment: comment.txt (text/plain), 12.59 KiB.
[12 May 2009 9:27]
Zhenxing He
Here is my comments on the translation, I had to say that I'm not quite sure about some of the translations, so please don't hesitate to argument! Thanks!
[13 May 2009 2:54]
shanyan baishui
Hi Zhenxing He, Thanks for your careful review and useful suggestions! Mostly I agree with you, bus there still some little problem. 1) > I think it's better to not translate commands, variable, arguments, options or data types Only commands is ok, but I thought, why we do this translate, we wanna Chinese users can use MySQL easily. As we know, not only developers use MySQL, more and more webmasters using MySQL, but when an error occurs, most of them still know the hows but not the whys. So if possible, I think translate them, then add the original uppercase commands, variable, etc.. in () is better. 2) Of course "table" is "表", as the reason of 1), I think "数据表" is more appropriate to let them know what it is. We need translate them exactly, but translate is not exam, also need fit the language style. 3) I don't know when, where, why and how the word "native" is translated to "原生", mabye from Native XML? but more and more "native support" translated to "原生支持", even "native" means "本地", and I also think "原生" is more appropriate to explain that. 4) Single "key", I'm not sure it's equal or not to an "index", but one example that is when CREATE TABLE use INDEX, that's actually is a KEY, so I prefer use "索引" not "键" to explain that a "key" do what. All above is a short of reply for your comments, and hope I can finish all reply at this weekend. I must finish my work of this week first. Thanks again!
[17 May 2009 10:53]
shanyan baishui
Hi everybody, I'm sorry for I have to stop work on this now. Our company have some busy projects to do. I will come back asap, maybe 2 - 4 weeks. Thanks!