Comment 1 for bug 266418

Originator: YES

Gentlemen, I have figured out how to use the poorly documented
transcheck command, and the winner is....
$ for i in $(cd messages;ls); do echo -n $i:\ ; bin/transcheck -q $i;done
ar: 15 warnings in 2 files
ca: 51 warnings in 4 files
cs: 2 warnings in 1 files
da: 17 warnings in 2 files
de: 38 warnings in 10 files
es: 40 warnings in 6 files
ja: 0 warnings in 0 files
...
sv: 50 warnings in 2 files
tr: 21 warnings in 2 files
uk: 17 warnings in 2 files
vi: 9 warnings in 3 files
zh_CN: 31 warnings in 4 files
zh_TW: 93 warnings in 10 files

That's right, zh_TW, another gold medal.

Actually it appears your whole approach is wrong.
With entire .html and .txt files to be translated, there will always
be missing buttons, etc. If instead using just strings in .po files,
if a message isn't translated, at least the English will be shown to
the user.

Anyway how terrible to have unlucky languages with missing buttons.

Let's see how MediaWiki does this. There is just one template, and the
stings are translated only.

Doesn't that make more sense? You program's functionality shouldn't
vary by language, but just the strings that describe the
functionality.

If one wants to customize, then one should customize the template,
affecting all languages.