Tracking bug.
Draft requirements:
https://www.mediawiki.org/wiki/Visual_editor/Bidirectional_text_requirements
Feel free to comment on them and edit them.
Version: unspecified
Severity: normal
See Also:
https://bugzilla.wikimedia.org/show_bug.cgi?id=49998
https://bugzilla.wikimedia.org/show_bug.cgi?id=49999
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| Bump version to 1.4.2 due to bug in osv cli | repos/security/gitlab-ci-security-templates!26 | sbassett | T351263-bump-osv-version-due-to-error | main |
Submitted an application for GSoC2013 to resolve this. More information available here: http://www.mediawiki.org/wiki/User:Mooeypoo/GSOC_2013_Proposal:_RTL_Support_in_VisualEditor
(Apologies for the bug submission mixup!)
Deployment to logged in users of Hebrew Wikipedia is in two days.
https://meta.wikimedia.org/wiki/Tech/News/2013/30
GSoC "soft pencils down" date was yesterday and all coding must stop on 23 September. Has this project been completed?
(In reply to comment #8)
GSoC "soft pencils down" date was yesterday and all coding must stop on 23
September. Has this project been completed?
Moriel should be writing a detailed summary now, but in short:
There will always be more RTL bugs in VisualEditor and in the rest of the Wikimedia software, so this tracker bug must not be closed. But this GSoC project definitely achieved its goal. Big, big thanks to Moriel, and to the VisualEditor team people who helped her do this - Inez, James, Roan, Krinkle, Trevor and all the rest.
If you have open tasks or bugs left, one possibility is to list them at https://www.mediawiki.org/wiki/Google_Code-In and volunteer yourself as mentor.
We have heard from Google and free software projects participating in Code-in that students participating in this programs have done a great work finishing and polishing GSoC projects, many times mentores by the former GSoC student. The key is to be able to split the pending work in little tasks.
More information in the wiki page. If you have questions you can ask there or you can contact me directly.
Note that almost all of the blocking tasks for this are wrongly filed; the vast majority are about the language of the user interface, not about the content. The former should be moved to VisualEditor-InterfaceLanguage; the latter to VisualEditor-ContentLanguage, and this tracking task shut down.
In Bugzilla it was useful to have this separate tracking bug to separate VE RTL bugs because there are a lot of them, and it's convenient to see just the non-VE RTL bugs. (There are also such trackers for Semantic MediaWiki and for the apps.)
I'd rather not shut it down entirely, but remove the word "content" from the title. Also, it doesn't have to be a tracking task, but an RTL tag, which would also replace T2745, and then we won't need a special tag or task for the combination of VE and RTL.
Why not have a tag called "RTL issues" then? This can be applied to tasks in all projects, rather than have this disaster of complication.
RTL content issues are often very hard to fix; RTL interface issues, however, are generally easy oversights in our usual work. Jumbling them together makes the hard tasks get less attention and priority.
Yes, I support it. I'll probably ask the Phab gurus for advice with this soon. (Not the most important thing on my plate at the moment.)