- From: Tomer Mahlin via GitHub <sysbot+gh@w3.org>
- Date: Sun, 30 Apr 2017 11:35:27 +0000
- To: public-i18n-archive@w3.org
@behnam thanks a lot for the detailed and swift response. I understand why you decided to exclude text rendering in the context of a programming language from the scope. Still, with your kind permission I would like to share several observation (by doing so I have no intention to affect your decision): 1.IDE moved to web for quite a while. Editing of text as part of program source code happens in web based editors. For example: - https://microsoft.github.io/monaco-editor/ - https://ace.c9.io/ 2. Web documents also undergo transformation. This goes beyond: - a simple transition of various office software to web based world (Google Docs, IBM Docs etc.) - document becomes a live creature with its own life cycle. Several people can simultaneously work on the content of the same document and simultaneously author different portions of it. In many cases document is served as an execution environment for data scientists. For example Jupyter notebook (http://jupyter.org/) may include both: - rich text paragraphs (which are characteristic of classical document or e-book) but also - pieces of code which will be executed inside the document itself. Results of this execution will be also embedded in the body of the same document (result of execution may be a text or a chart). Reminds me of living / interactive newspapers from Harry Potter movies (https://www.youtube.com/watch?v=xaBEFqFVSE8). In other words web documents and e-books quite often include code written in some programming language. I never dreamed of having localized programming language. I am aware of existence of localized language for creation of logical rules (if my salary is > 100 K and my ... then take mortgage (500 K) from bank ...), but not a programming language. Thus my assumption was always that programming language syntax / flow will be always LTR. However, as it is pointed out in [UAX #31: Unicode Identifier and Pattern Syntax](http://unicode.org/reports/tr31/#R3) non Latin characters can be still present in such contexts (at least as part of constants / comments). [Monaco editor](https://microsoft.github.io/monaco-editor/) handles such cases reasonably well. Namely it preserves the syntax of programming language on display and by doing so contributes tremendously to readability of the code (for more details please see: https://github.com/Microsoft/monaco-editor/issues/280). However even Monaco editor does not handle in any special way the constants / comments. They all are displayed with LTR text direction. This of course is not optimal for languages such as Arabic. I am closing this issue as irrelevant. -- GitHub Notification of comment by tomerm Please view or discuss this issue at https://github.com/w3c/alreq/issues/113#issuecomment-298226972 using your GitHub account
Received on Sunday, 30 April 2017 11:35:34 UTC