- From: Behnam Esfahbod via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 May 2017 00:16:14 +0000
- To: public-i18n-archive@w3.org
Right, @tomerm. Generally agree on most of the issues mentioned. There are few different situations discussed in your comment, so let's talk about each separately. ### a) Block-level embedding in an rtl/bidi document When images/videos/listings (like code examples) get embedded in a document. We will be covering this in *Page layout chapter*. ### b) Block-level embedding of rtl/bidi content inside another document I think this is an area that we can also cover in the *Page layout chapter*. ### c) Inline rtl/bidi content in a non-text context These non-text context are what Unicode calls a *higher protocol* and it's something that's totally application-dependent. For example, as mentioned in https://github.com/Microsoft/monaco-editor/issues/280, you may want to enforce LTR direction on all lines of a programming language, and then apply an auto paragraph direction detection on every string literal. As much as I agree that there's a lot of room for work here, I think it's very application specific, and one of those areas that has no precedent nor any existing common practice, needing experiments and prototypes to get started. I think this lack of existing information would be the main reason that we cannot cover this as a Special Case in ALReq, at least not in version 1.0. ### d) Cursor movement in bidi documents This is one of the recurring issues, in general. For example, there still exist many problems with this in OpenOffice/LibreOffice authoring applications, specially when you need to jump words or lines. The TF being focused on *layout*, I'm afraid we don't have plans for any authoring/editing UX material. The i18n WG may have plans about that for the near future. (@r12a?) -- GitHub Notification of comment by behnam Please view or discuss this issue at https://github.com/w3c/alreq/issues/113#issuecomment-298465951 using your GitHub account
Received on Tuesday, 2 May 2017 00:16:20 UTC