Feature #107
closedinstall MediaWiki translate extension
100%
Description
We need to install the following extension for our public wiki: https://www.mediawiki.org/wiki/Extension:Translate
Related issues
Updated by Alexander Werner over 10 years ago
- Blocks Feature #465: update MediaWiki to 1.23 added
Updated by Alexander Werner over 10 years ago
Deferred until tested with MediaWiki 1.23
Updated by Dennis Roczek over 10 years ago
- Blocks deleted (Feature #465: update MediaWiki to 1.23)
Updated by Dennis Roczek over 10 years ago
- Blocked by Feature #465: update MediaWiki to 1.23 added
Updated by Adolfo Jayme Barrientos over 10 years ago
Please consider installing the TranslationNotification extension as well. It would allow translators to be notified via e-mail about important pages that need translation, such as the release notes.
Updated by Robinson Tryon over 10 years ago
Adolfo Jayme wrote:
Please consider installing the TranslationNotification extension as well. It would allow translators to be notified via e-mail about important pages that need translation, such as the release notes.
+1
It sounds like installing the Language Extension Bundle is the suggested way of setting-up for multilingual wikis:
https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle
TranslationNotifications is (I believe) a separate extension:
https://www.mediawiki.org/wiki/Extension:TranslationNotifications
Updated by Florian Effenberger almost 10 years ago
Any chance to have a look at this before Christmas?
Updated by Dennis Roczek almost 10 years ago
well it depend on my time. but for the case alex doesn't have the time, I will likely find the time int he holidays. (so I would only need access, but for that i have to send my sha key... :-P)
Updated by Florian Effenberger almost 10 years ago
Feel free to mail your SSH key to Alex, of course ;-)
Updated by Florian Effenberger almost 10 years ago
Did you get access already? If not, e-mail me your private key directly
Updated by Alexander Werner almost 10 years ago
- Status changed from New to Feedback
- Assignee changed from Alexander Werner to Dennis Roczek
Dennis, i need your SSH key please and a password generated with mkpasswd --method=sha-512 or
$ python2 $ import crypt; print crypt.crypt('PASSWORD','$6$HASH')
Updated by Dennis Roczek almost 10 years ago
Alexander Werner wrote:
Dennis, i need your SSH key please and a password generated with mkpasswd --method=sha-512 or
[...]
Yeah. Sry. I had some problems with my flat in the last few days and thus my spare time was eaten up. :-(
Will do it later. ;-) (I promise!)
Updated by Dennis Roczek almost 10 years ago
@alex and finally here is my ssh :-)
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCkkIkLOsDOvwkWSPIxPM+N1OHVV/6Hif4jrupQ/sxZ9ldFuTrT3oruoiuRyQ8T+/1zA7tpyvJYieF4V1JIq1NnMVY9S15e10nG2IwmqnyYZ3kfNkuSP1rl7ynjYPjVRjXK8a6k6llyAQMDt4i2CwGY8GN+sayEuSJ/0w1gjO9vef8HoXaHfPlbK5kO79cjlCaK4grHmoo4mINeWSGZU9OVSjn43+NEZHz3MJZPcHctpsDoQi+EVCpUGyDEcMFEMvZFFOjYKFa5V6xuE1S2BszWmTG90p9Xs5R0+mpgRNNOR6iVNcM8QkEf7NOgLdVzusU7eIRxjtrUAlizYBVWZOpn dennisroczek@libreoffice.org
Updated by Beluga Beluga almost 7 years ago
Robinson Tryon wrote:
It sounds like installing the Language Extension Bundle is the suggested way of setting-up for multilingual wikis:
https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle
This was requested just now by a contributor, the reason given:
"I’ve noticed that composing and editing Persian, an RTL language, is nearly impossible currently (you have to use several hacks to make it work)."
Updated by Eric Bright almost 7 years ago
Thank you Beluga and Dennis Roczek for reviving this issue. I certainly need that bundle if I, or any Persian-speaking editor for that matter, want to edit an RTL page.
The problem is that the wiki editor jumbles up everything in the “compose” area from left to right and sentences become almost unreadable there. One has to copy them into an external editor that also supports RTL, edit the text there, copy/paste them back in the wiki editor (which immediately scrambles up everything again), look at the preview, and repeat. It’s a tangled mess!
Not only that, but also any language tag such as {{fa}} {{fa-end}} that one might add to fix the published page, only affects the body part that is manually composed. All other auto-created parts, such as the table of contents, are still LTR in the published page.
Updated by Florian Effenberger over 6 years ago
Dennis, Guilhem, something you can have a look at maybe during next week?
Updated by Guilhem Moulin over 6 years ago
- Assignee changed from Dennis Roczek to Guilhem Moulin
- % Done changed from 0 to 90
Done: deployed and tested on test wiki, deployed to prod wiki. (I'll be on vacation starting at the end of the next week, and should problem arise I'd very much avoid getting a phone call during DebConf :-P)
See https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example for a tutorial. See also the language selector dropdown menu at the top right of the page.
The configuration is pretty minimal at the moment, depending on how it affects the load we'll need to see whether further optimization is needed.
How about ACLs? Should every user be allowed to translate, or should we create a new “translators” group or something?
Updated by Florian Effenberger over 6 years ago
How about ACLs? Should every user be allowed to translate, or should we
create a new “translators” group or something?
No educated guess here - can you poke Marina? She asked for that
extension recently, maybe she has an idea :)
Updated by Dennis Roczek over 6 years ago
Florian Effenberger wrote:
How about ACLs? Should every user be allowed to translate, or should we
create a new “translators” group or something?No educated guess here - can you poke Marina? She asked for that
extension recently, maybe she has an idea :)
do everybody (registered) to be open as much as possible; then we can see how this will work out. To restrict the stuff is easy and can be done later for the case it produces vandalism/spam/whatever.
Updated by Florian Effenberger over 6 years ago
No objections ;)
do everybody (registered) to be open as much as possible; then we can
see how this will work out. To restrict the stuff is easy and can be
done later for the case it produces vandalism/spam/whatever.
Updated by Guilhem Moulin over 6 years ago
- Status changed from New to Closed
- % Done changed from 90 to 100
Dennis Roczek wrote:
do everybody (registered) to be open as much as possible; then we can see how this will work out. To restrict the stuff is easy and can be done later for the case it produces vandalism/spam/whatever.
Fair enough, done and closing this :-)