From feedbacks in https://groups.google.com/forum/#!topic/i18n-zh/v_qLhCQDg1A:

• Use http://www.ikde.org/discuss/how-to-translate-kde/ as the KDE translation guide.
• Import some discussions over some specific usages of language, e.g. tones, into our guide.

On the GNOME l10n zh_Hant team page I found them using a silghtly modiifed version of zh_CN l10n v1.1, therefore we need to:

• Amend https://mail.gnome.org/archives/gnome-i18n/2015-September/msg00152.html to form a nice rationale, possibly translating into zh using MisakaIL-zh +legacyexpr +rime_hant_pinyin.
• In a polite tone, send the thing to https://groups.google.com/forum/#!forum/chinese-l10n or [email protected]. These two lists are linked together, and I prefer sending to the latter. In plain text, of course. I should either use MisakaIL-zh +legacyexpr +rime_hant_pinyin or MisakaIL-en@codespeak.

This is part of some thank-you — we've ported (huh) bunches of their translations to zh_CN.

• Also, I think I should add some examples for those modern fonts I talked about. For UI fonts, I expect sans-serifs with straight borders, i.e. 无喇叭口黑体, with other optimizations for reading on-screen.
  Source Han Sans, WenQuanYi & Droid Sans Fallback, plus Ubuntu are examples of that.

https://github.com/Warzone2100/warzone2100/tree/master/po

Their status bot seems down, so perhaps these are already at 100%.

Just pushed FileZilla zh_CN to the repo, with a quick fly-through to:

• Complete translation;
• Quick symbol/punctuation lint;

TODO:

• Full review;
• Periodical upload to upstream;

• We use Hybrid PDF. Don't leave stupid ODT backups.
• BUILD THE PDF ONLY WHEN YOU HAVE THE FONTS INSTALLED. You may build "preview" versions of the PDF if you don't, but you should not change the current symlink. You may still overwrite the ODT.
• Never break URLs. If you move the directory around, create a symlink or a 301.

By the way I absolutely hate the aosc- part in the current aosc-l10n/ dirname designation. It's a terrible idea to make it AOSC-specific.

The lack of translations for GnuPG tools and frontends is a great obstacle for advocating the use of cryptography to protect personal data in China.

Kleopatra from KDE is a full-functional frontend for GnuPG and is used by Gpg4win. But the translation is incomplete. I'm working on the translation of Kleopatra on my spare time, and don't expect me to finish this project before 2017.

Is there anyone who has time to send an E-mail to the upstream to notify the contributors of KDE-CN not to waste time on this program? If so, please remove the "help wanted" label afterwards.

Foo Bar. And don't bring pots in.

https://groups.google.com/forum/#!topic/i18n-zh/2E8tkwLkKqI

coreutils ~70 strings
nano ~40 strings, scattered whitespace changes

nano 100% (delta ~100, many changes, ws), coreutils 75% (delta ~150, ws)

• bfd
• binutils
• ld (all done)
• gold
• gas

Let's fill gold a bit by using some Compendium data from -- and only from -- the other 3.

• $2%s -> %2$s
• Underscores cross the characters. (PDF exported with LibreOffice 6.0.4 looks OK, but not sure if it's because required fonts are missing)
• some lines are too dense and characters are overlapping. (same as above)
• POEdit -> Poedit

For example, there seemed not to be any description on whether to put ellipses first, or the accelerators first.

On Ubuntu Distro listing pages, LP provides a column called "Changed", which shows the number of strings changed in Ubuntu.

Perhaps we should send these changes back upstream, especially if upstream has no zh_CN/TW translations:

• https://translations.launchpad.net/ubuntu/xenial/+lang/zh_TW/+index
• https://translations.launchpad.net/ubuntu/xenial/+lang/zh_CN/+index

(Click on the column header to sort by this column)

• NetworkManager
• gnupg2 TW2CN

Here are the requirements for v1.3 release:

• Correct language name.
  • 简体中文 -> 大陆简中 OR 中文（**）
  • Simplified Chinese / Chinese ([Ss]implified) -> Chinese (China) / PRC
• Parentheses: Use the MS Way.
  • No spaces for Hotkey Indicator ASCII PAR.
  • Use CJK PAR for CJK.
  • Use ASCII PAR for Western text, things like (R) and code (which should always be as-is).
• Tool: Translate Toolkit.
• Separate chapters for Styling and File Format.

It will be tricky to keep the page count small then.

We see a lot of misleading translations in grep --help:

-z, --null-data a data line ends in 0 byte, not newline
-z, --null-data 一个 0 字节的数据行，但不是空行

-o, --only-matching show only the part of a line matching PATTERN
-o, --only-matching 只显示匹配PATTERN 部分的行

--line-buffered flush output on every line
--line-buffered 每行输出清空

etc.

Complete review required.

Yes we need to do some KDE work to sample more data and hopefully identify more existing problems…

I really should spend some time reading MS chs&cht, W3C CLREQ & JLREQ too.

And this need to be patched for 1.5.1:

• Sec 1.0: add links to gnome, kde and launchpad translation teams; links to transifex and crowdin.
• We need a sixth author or et al won't work. Yes Bai you have been chosen.

Oh yeah, and we can use the pretty word living standard instead of proposed draft.

And I doubt if those translations in our crowdin are really usable……

@MingcongBai We need to keep an eye on TP..

• Dump an FODT
• OpenCC it
• Fonts:
  • FandolSong -> cwTeX Ming Q
  • Source Han Sans CN -> TW
  • Inziu Iosevka SC -> TC
• Replace all kinds of 大陸簡中
• Punct Rules
• +tw.alpha0
• syntax..
• +tw.beta0
• ms chs-cht rule diffs…
• +tw.rc0, proposed draft

If transifex, I will regen workflow.svg, and do all those manual svg edits again.

• Import edits found in zh_TW:

  1. 遇到說明英文標點的訊息時，除了翻譯為中文外，請在譯文中加入該標點，並在標點前後加上中文 (較建議) 或英文引號。例："seperated by common" 即：以半形冒號「:」隔開；或以半形冒號 ":" 隔開
  2. 遇到說明選單的訊息時，例如：System > Administration ，可以見到頭文字大寫，這麼做除了模擬選單本身頭文字大寫外，還能在同是小寫的句子中吸引讀者的目光。因此請使用上下引號將選目內容括住，以達到同樣效果：「系統」>「管理」，並請注意標點之間無需空格。另一種表示方式為 [系統] > [管理]，括號與 > 之間需添加半形空格隔開，但由於 [] 括號並非規範的中文標點符號，因此此種表達方式較不建議使用。

  zh_CN:

  1. 遇到说明英文标点的消息时，除了翻译为中文外，请在译文中加入该标点，并在标点前后加上弯（GUI）或直（CLI）引号。例如seperated by comma译为“以半角冒号‘:’隔开”[a]，或“以半角冒号 ":" 隔开”。
  2. 遇到说明菜单的消息时，例如：System > Administration ，可以见到首字母大写，这样做除了模仿菜单本身首字母大写外，还能在同是小写的句子中吸引读者的目光。因此请使用半角方括号括住，如 [系统] > [管理]，括号与 > 之间需添加半角空格隔开。

  a: 这里是因为引号嵌套用了单引号。

• Mention the General Punctuation chart.

• Link to v1.1 and twfork

I like the VERY OLD warning. It's hilarious.
(Oh yes I love such upstream, even for such super-retro-style app.)

Unfortunately I am too lazy to run configure and build the pot now. The attached zh_*.po are updated according to ja.po (pot in 2015).

All I want is actually this:

警告：

此版本的 xscreensaver 非常旧了！
请升级！

http://www.jwz.org/xscreensaver/

（如果这是您的发行版提供的最新版，那么你的发行版在
给你添乱。编译安装。）

po.zip

Put them in GH wiki maybe?

Use BYVoid/OpenCC#130 way, and filter out the words manually.

IT and Free License need to be processed.

These locales confirm perfectly to the locale code @variant directives..

libexif really stands out on translationproject.org by marking their translation "externally managed" (better known as "last update in 2011"). Sending patches based on a CVS checkout in SF bugtrackers is gonna be fun.

http://libexif.cvs.sourceforge.net/viewvc/libexif/libexif/po/zh_CN.po?view=markup

Like gutenprint, there are a lot of "regex-able" translations. Only do it when you are bored, or when you are fed up with green JPGs.

Brunchpad copy seems equally untranslated: https://translations.launchpad.net/ubuntu/+source/libexif