Last modified: 2014-01-03 16:28:25 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T55361, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 53361 - clever support for direction in CodeEditor
clever support for direction in CodeEditor
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
CodeEditor (Other open bugs)
unspecified
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: rtl
  Show dependency treegraph
 
Reported: 2013-08-26 18:40 UTC by Amir E. Aharoni
Modified: 2014-01-03 16:28 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Amir E. Aharoni 2013-08-26 18:40:22 UTC
Most programming languages are left-to-right, so dir="ltr" should be the default for CodeEditor. However, some programming languages are right-to-left, for example qlb and others (see [[Non-English-based programming languages]] and search the page for Arabic), and they should be supported, too. The direction should probably be a parameter when initializing the editing control.
Comment 1 Ori Livneh 2013-08-26 20:44:56 UTC
Some context: https://gerrit.wikimedia.org/r/#/c/80707/
Comment 2 Derk-Jan Hartman 2013-12-31 10:35:13 UTC
We don't support anything but JS/CSS and Lua right now right ? So this is highly theoretical for now ?
Comment 3 Brion Vibber 2014-01-03 16:28:25 UTC
Use of explicitly RTL programming languages would be highly theoretical, I would think. :) But neat, if anybody wants to run a wiki using them we'd love the patch I imagine.

Full bidi is however useful for "regular" programming languages that include comments or strings in RTL languages, however.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links