Imporve language converter systems (eg. between simplified and traditional Chinese)
Problem: LanguageConverter is usually not used in system messages and translatable pages. For example, editing a MediaWiki-namespaced page "xxx/zh" does not affect "xxx/zh-cn", "xxx/zh-tw", "xxx/zh-sg" etc, which means, readers whose interface language is "zh-sg" sees the original content that is defined by the software, instead of the converted version of "xxx/zh". In Chinese wikipedia, bots are used to automatically convert and create "xxx/zh-cn", "xxx/zh-tw", "xxx/zh-sg" ... pages according to the content of "xxx" or "xxx/zh"
Proposed solution: Convert contents automatically when displaying system messages, without the need of creating subpages for each language variant.
Who would benefit: Users using language-converter system, for instance, users speaking Chinese
Where's the scope of this proposal? Does it mean all user interface messages in MediaWiki should be handled by LC? If so, I'm afraid I won't support this. This add extra complexity to the software.--Tranve (talk) 03:49, 21 January 2022 (UTC)[reply]
As I've said before, the LanguageConverter doesn't have many benefits when it's used to handle large sets of short messages, because we have to add a number of extra conversion rules to every message. Tranve (talk) 03:54, 21 January 2022 (UTC)[reply]
@Tranve: Converted texts may be caches as soon as the pages are created, which works like some bots or gadgets in WP, which creates specific subpages that stores converted text. The LC is used for message pages created, or messages that override default messages. That would not be too much burden for the server. And @Thingofme: you may refer to mw:Special:MyLanguage/LanguageConverter. --SolidBlock (talk) 14:14, 22 January 2022 (UTC)[reply]
Support translation system, followed by mandatory review by converter – because robotic translation has real problems, plus issue of citations – and need to see which images can come along with text from original language Aboudaqn (talk) 20:27, 28 January 2022 (UTC)[reply]