Created attachment 60018 [details] Simplified Chinese (zh_CN) translation Please see the attached file, which is an updated version of Simplified Chinese (zh_CN) translation of latest PulseAudio. The POT file was grabbed from transifex.net.
Hi, Aron. You can grab the latest po file [1] as a template to update your translation file. http://cgit.freedesktop.org/pulseaudio/pulseaudio/tree/po/zh_CN.po
Well, I also found that the translation has been updated by a red hat employee. Maybe you can review his translation and submit a new po file.
Hi Tseng, I prefer to have the translation submitted by the RH employee get reverted. Some time ago, I argued to her director about the quality of some work she had done for GNOME, and more importantly she ignored the community and asked the component maintainer (who is another RH employee) to add her translation directly to the git repo neglecting the community translation team, who are maintaining the project very actively in that mean time. In the current translation of PA, I'm wondering why she would translate "sink" into "漏". This makes no sense in our case and actually "audio sink" should be translated into "音频信宿", which is a already being accepted as a terminology by many published books. "sink" is "水槽" in Chinese as a noun, and "漏" is usually a verb means "leak". "音频" is "audio" and "信宿" means the final link of a cycle in which information flows dynamically, which is what "sink" means here IMHO.
Hi, I updated the translation in d-i. https://l10n.gnome.org/media/upload/PulseAudio-master-po-zh_CN-315803_SgN6B8w.merged.po https://l10n.gnome.org/vertimus/PulseAudio/master/po/zh_CN
Thanks! Since you did not send a git-formatted patch, I have to manually set the commit author. Should it be YunQiang Su, since you said you updated the translation, or should it be Luo Lei, who is mentioned in the "Last-Translator" field in the .po file?
I now applied the tranlation with "YunQiang Su <wzssyqa@gmail.com>" as the author.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.