Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#26638 - {wiki} Proposal: Translate extension

Attached to Project: Arch Linux
Opened by Atilla ├ľNTA┼× (tarakbumba) - Wednesday, 26 October 2011, 19:57 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 22:03 GMT
Task Type Feature Request
Category Web Sites
Status Closed
Assigned To Pierre Schmitz (Pierre)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


Hi. I'm trying to translate some articles into Turkish. While looking to the net, i've found a wiki extension named Translate extension. Advantages of this extension as well as the contact information of authors can be found here:

I want to improve wiki by translating important articles for native Turkish speakers who dont know English. Currently, wiki policies for non-english people are weird. People can't look into articles, because of enlish only titles. Also, templates etc. are only English too.

Further info:
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Saturday, 02 November 2013, 22:03 GMT
Reason for closing:  Won't implement
Comment by chaofeng (rainofchaos) - Wednesday, 07 December 2011, 06:34 GMT
This is a good idea. I have some translation work in both Arch Wiki and KDE userBase wiki(using this extension). For my experience,

1. Internal links will change to translated version automatically. For example, all translated page link to AUR using the same link: [[Special:myLanguage/AUR|AUR]]. Before translated, this link lead to the English page. After translated to zh_CN, this page will go to the translated zh_CN page. Very convenient.

2. Whole page is splite to small translate units. If some English parts is changed, these small units will be marked fuzzy. So I do not need to look deep into the history for all the diffs.

3. Good language statics, see:

4. Translation speed. The edit interface is very user friendly. English part and i18n part are listed together. As for me, I can translate 50% ~ 100% more messages in KDE user base than in Arch Wiki.

1. Wiki work flow change. After using this extension, all changes should first go to the English part. And then link back to non-English messages. Or the system may be messed up.

2. External language wiki such as fr de can not benefit it. Maybe move them back is a solution. But since they are just moving out some time ago ...

3. Convert current {{i18n}} to this extension is a great work. For most already exist i18n pages, it is impossible to convert automatically.

My conclusion:
A kde user base translation system is a feature I dreamed of from a long time ago. If this Proposal is passed, I am willing to help.
Maybe we can find a incremental transition path. Newly created message use new extension and old pages changed to new system one by one.
Comment by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 22:03 GMT
Non-Englsh wiki pages should be moved to separate wikis.