Please note actions by [[User:Liuxinyu970226]]

Thanks Jimmy Xu for letting us know; we certainly have to make this locale more stable.

As far as I know, Cwlin0416 has stopped edit warring. If some user edit wars without having had some discussion, just report the fact here and I'll remove their translating rights for the time being. (To make an example, Arthur2e5 above has explained his reasons well enough for the mentioned translations.)

If translators are split only/mostly according to their linguistic background (Taiwan, Hong-Kong and what not), then we should seriously (re)consider giving each block their locale. Is this the case?

Nemo (talk)08:24, 16 October 2016

Good point! Well, zh-hk is actually available: https://translatewiki.net/wiki/Special:Translate/core?group=core&language=zh-hk&filter=%21translated&action=translate , so the question is just zh-tw?

Liuxinyu970226 (talk)08:33, 16 October 2016
 

The thing with zh locales is that one would really like to use automation given that most differences come not from sentence structures, but from word choices. Split locales mean split storage, and as long as there is some newcomer is obsessed with getting the percentage to 100%, we get whole lots of redundancy.

A relevant system where mostly automated conversion across zh variants is MediaWiki's LanguageConvertor.

Arthur2e500:45, 17 October 2016

I don't think LanguageConverter should be implemented here, since it'd be more and more tricky (please, believe me, /zh pages are really bad in MediaWiki.org as per phab:T106131#1481796)

Liuxinyu970226 (talk)09:57, 17 October 2016

I should have clarified that I am not talking about the mediawiki.org site but the software component.

Yes, the commonly-used form of LC which operates on nearly-parsed wikitext is bad for most usages other than HTML documents. Yet this does not rule out the possibility of using a more constrained interface[1] like a "dumb" LC (e.g. translate($text, $variant)), with a different text scanner passing text needing conversion to LC.

Some extra release-time work will be needed if TWN is used this way with language conversion, as it's unlikely that anyone would want to run some ./do_ui_language_generation.sh on what they have downloaded. Technical difficulties can be overcome as experiments and PoCs appear; it's mainly the consensus that needs to converge.

Notes[edit source]

  1. An interesting way of making LC HTML-dumb is through <pre>-{}-blah...</pre>.
Arthur2e517:38, 17 October 2016
 

As for the obsession with 100 %, it would be enough to make the entire language's messages "optional". I believe there is no such configuration yet, but it would possibly not be that hard.

Nemo (talk)13:22, 30 October 2016
 

To: @Nemo:, @Liuxinyu970226:, @Jimmy xu wrk:

I'm agree to had some discussion before edit, but there is no list about terminology which zh-wiki uses, currently one which is i made, all zh-wiki wants is do not edit any translation, all accuse from zh-wiki is i'm making vandalism. is this right?

I'm not intentionally to start edit warring. But difference between Simplified Chinese and Traditonal Chinese not only word but also region (Taiwan, Hong Kong). Before i edit Traditional Chinese, there is much translations is not suitable because translations are just following Simplified Chinese, "even some translations are only for zh-wiki". Although change translation will affect some documentation which zh-wiki currently use, this is helpful to MediaWiki Traditional Chinese users growth.

MediaWiki is not only for Wikipedia but also open source project, MediaWiki's user not only Wikipedia. I'm not "don't care what zhwiki uses", but i'm care Mediawiki Traditonal Chinese users uses more than zh-wiki.

Cwlin0416 (talk)09:22, 29 October 2016