Created attachment 137388 [details] zh_CN localisation (Fontconfig) Attached below are the two zh_CN translation files generated from current master, running `make update-po` from both po and po-conf. While I made the first translation draft, Mingye Wang and Dingyuan Wang have provided with valuable suggestions to refine the translation. P.S. Will Fontconfig's localisation work be moved under the FreeDesktop.org project on Transifex?
Created attachment 137389 [details] zh_CN localisation (Fontconfig-conf)
More translation revisions will be made in the near future...
No plans to use any translation platforms at this moment though, maybe in the future. Anyway, added translations into git. thanks!
Created attachment 137442 [details] zh_CN localisation (Fontconfig, v2)
Created attachment 137443 [details] zh_CN localisation (Fontconfig-conf, v2)
(In reply to Akira TAGOH from comment #3) > No plans to use any translation platforms at this moment though, maybe in > the future. > > Anyway, added translations into git. thanks! Hi, could I bother you to introduce the v2 translation works to Git? We have made some minor fixes on the translations (specifically, reverting the translation of the long parameter names, which shouldn't be translated in the first place; and added some brackets around variables, per zh_CN l10n convention). Also, could you guys look into fixing the .pot header so it doesn't use placeholders for your project name and copyright year?
I can't see any difference in the translations for -conf. can you make the git-format-patch based file instead of putting the indivitual files here?
(In reply to Akira TAGOH from comment #7) > I can't see any difference in the translations for -conf. can you make the > git-format-patch based file instead of putting the indivitual files here? This will be the commit... And yes, nothing's changed with -conf. my bad. https://github.com/AOSC-Dev/fontconfig/commit/e5f4dea16a62bd2a43c9d38333ad911616017580
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.