-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Simplified Chinese language file #440
base: master
Are you sure you want to change the base?
Conversation
Apparently his changes are based on the previous incomplete translation (his own version) and he only added the missing entries. So the result is that he reverted most changes that I made. I strongly disagree with these changes. After going through them, I don't think I see any good edit. As you see, I spent a lot of time doing research into every entry, so I fully understand the meaning of every entry. I searched on Internet and digged into the source code. The translation toolkit is the proof. Reducing the column width is also a proof. Apparently he did no research, nor did he check my toolkit, so his changes brought a lot of mistakes back. Not to mention I have decent knowledge about media files - I know video processing (e.g. VapourSynth), encoding (e.g. x264, x265), container formats, muxing and demuxing (e.g. mp4 and mkv) etc. You see, I included doom9 links in the toolkit. I deal with media files a lot, so I know what people use MediaInfo for, and what terms are appropriate. Moreover, I myself have much exprience in translating. I helped translate other computer softwares and I know how to avoid bad translation. No offense here, but I think my English expression is better and more fluent than his. Regarding the punctuation styles, I go with half-width ones because they make the information look shorter. In my opinion, easy to read is more important than style preference. But after all, the punctuation he used himself was inconsistent. He used half-width question marks and parentheses. I guess it's because if he used full-width ones, the strings would be too long and too "spacious". I still recommend half-width ones. I know that detailed explanation about each entry is needed to convince you, but according to my experience, it would be too time-consuming, not to mention the time that I already spent on the translation work. My suggestion is to reject this change. I believe he had better compare my translation, his translation and the original English text, check my translation toolkit, and provide reason for each change. Thank you. |
I currently don't have strong opinion, more on discarding this change except one thing I forgot to mention from feedback:
It may be good to have this system of Chinese + original English, I don't see how it could hurt a lot. |
My opinion from #418 (comment):
I'm not against Chinese + English, but he had better do thorough research and figure out the correct translation in Simplified Chinese. Using the current "converted" translation from Traditional Chinese is similar to using Brazilian Spanish for Castilian Spanish, etc. It's just not right. |
Update from the translator having started the translation.
Comments from him:
The changes I have made:
@stevenlele please review and comment.
Please note that I have absolutely no idea about what are the changes and what is the "best", I am just trying to have the best translation file for my zh-CN users.