Viability of unusual directionality (e.g. RTL) in General Information Exchange

[MasterInQuestion]

    Follow-Up: https://github.com/microsoft/vscode/issues/11770#issuecomment-1361202820

    Relevant demo: https://github.com/MasterInQuestion/attach/commit/e5ddd9778eccefbb394601c0e17b872c6a686902

[MasterInQuestion]

    It appears Tibetan is also sort of RTL property (perhaps even directionality-free like Chinese), despite being asserted LTR.

    https://earlytibet.com/wp-content/uploads/2014/02/itj629_colophon.jpg
    https://earlytibet.com/2014/02/04/the-original-bodhicaryavatara/
    .
    https://www.pinterest.com/pin/647462883949159168
    https://inkessential.blogspot.com/2009/03/seal-script.html
    https://babelstone.co.uk/Phags-pa/Overview.html#Tibetan

    https://r12a.github.io/scripts/tibt/bo.html#direction
    https://r12a.github.io/scripts/tutorial/summaries/tibetan

[MasterInQuestion]

    [ Quote iAhmadKarmola @ CE 2023-11-15 00:34:18 UTC:
https://github.com/microsoft/vscode/issues/11770#issuecomment-1811611927
    ]
<^>    I sincerely couldn't understand how could such be even considered the acceptable working state...
    Tricky seeking, in particular after soft-wrap.

[MasterInQuestion]

    Hi, @iAhmadKarmola.
    Would you mind giving some comments on this? (merely for linguistic research)
    Thanks.

[iAhmadKarmola]

    Hello, I did not understand what you mean.
    If you mean that you want documents to support RTL languages in VS Code or documents to be completely right-to-left, I answered in the comments below:
    https://github.com/microsoft/vscode/issues/11770#issuecomment-1811611927
    https://github.com/microsoft/vscode/issues/11770#issuecomment-1813469645

[MasterInQuestion]

    Thanks anyway for your participation.
    The title of this thread much says all. (please trace the links also)

    In brief, how do you read such BiDi (Bi-Directional) content?
    Do you really think current BiDi implementation of things acceptable..?

[MasterInQuestion]

    I have derived a set of typical RTL characters (APH: Arabic, Persian, Hebrew) practically in use:
    Based on the referential keyboard implementations on Google Translate:
    |*| https://translate.google.com/?hl=en&sl=ar
    |*| https://translate.google.com/?hl=en&sl=fa
    |*| https://translate.google.com/?hl=en&sl=iw

    /[א-תء-غـ-ْ٠-٩ٵپچژکگی۰-۹]/:
[[
א
ב
ג
ד
ה
ו
ז
ח
ט
י
ך
כ
ל
ם
מ
ן
נ
ס
ע
ף
פ
ץ
צ
ק
ר
ש
ת
ء
آ
أ
ؤ
إ
ئ
ا
ب
ة
ت
ث
ج
ح
خ
د
ذ
ر
ز
س
ش
ص
ض
ط
ظ
ع
غ
ـ
ف
ق
ك
ل
م
ن
ه
و
ى
ي
ً
ٌ
ٍ
َ
ُ
ِ
ّ
ْ
٠
١
٢
٣
٤
٥
٦
٧
٨
٩
ٵ
پ
چ
ژ
ک
گ
ی
۰
۱
۲
۳
۴
۵
۶
۷
۸
۹
]]

    And among which we have the "French F and English F"...
    https://github.com/MasterInQuestion/Markup/blob/main/AAA.htm

    See also:
    |*| https://unicode.org/charts/nameslist/n_FE70.html
    |*| https://unicode.org/charts/nameslist/n_FB50.html

[mohmmadView]

https://github.com/microsoft/vscode/issues/11770#issuecomment-1987347003

[MasterInQuestion]

https://github.com/microsoft/vscode/issues/11770#issuecomment-1989415954

[MasterInQuestion]

    @mohmmadView,
    I'm interested in how RTL languages like Arabic are supposed to be parsed, when interleaving LTR content.
    (e.g. natively, the numeral digits; and English etc.)

    Would you mind providing some insights? Thanks.