Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use of Arabic Reordering in text editing #497

Closed
behnam opened this issue Oct 3, 2017 · 3 comments
Closed

Use of Arabic Reordering in text editing #497

behnam opened this issue Oct 3, 2017 · 3 comments
Labels
close? The related issue was closed by the Group but open here needs-resolution i18n expects this item to be resolved to their satisfaction. s:utr53 t:typ_misc 8.7 Miscellaneous

Comments

@behnam
Copy link
Member

behnam commented Oct 3, 2017

This is a tracker issue. Only discuss things here if they are i18n WG internal meta-discussions about the issue. Contribute to the actual discussion at the following link:

§ https://www.unicode.org/review/pri359/

@r12a r12a added pending Issue not yet sent to WG, or raised by tracker tool & needing labels. s:utr53 labels Oct 4, 2017
@behnam
Copy link
Member Author

behnam commented Oct 13, 2017

Submitted this via the online form:


Subject: Feedback on Proposed Draft UTR #53 — Revision 1
Status: Liaison Contribution - W3C i18n WG

Using UAOA in Text Editing

On Section 5.6 “Other uses for UAOA”, we have:

UAOA is very useful in implementations of backspacing in cases where there is no external information available about the original order in which the text was entered.

For an average user of modern languages using the script, reordering the marks entered on a keyboard would be unexpected behavior.

Basically, the document is suggesting that when user authors a text file with Arabic Marks put in a specific order, when the files is closed and reopened, the backspace should behave differently from the previous session.

Also, it is not clear at all if UAOA will be useful in a text editing scenario. The claim for UAOA to be "very useful" needs some evidence, like existing implementation or some other data to support it.

From the language and examples of the document, it looks like the usage of the algorithm is too focused on one application, Quranic text, and the claims are related only to that specific application of the script.

@behnam behnam closed this as completed Oct 13, 2017
@r12a
Copy link
Contributor

r12a commented Oct 16, 2017

Reopening, because the WG will want to track this.

@r12a r12a reopened this Oct 16, 2017
@r12a r12a added tracker i18n is following a discussion, but doesn't require resolution. and removed pending Issue not yet sent to WG, or raised by tracker tool & needing labels. labels Oct 16, 2017
@r12a
Copy link
Contributor

r12a commented Dec 11, 2017

Some editorial work was done on the relevant section. Can we close this now?

@r12a r12a added the close? The related issue was closed by the Group but open here label Dec 11, 2017
@r12a r12a added the needs-resolution i18n expects this item to be resolved to their satisfaction. label Nov 16, 2018
@r12a r12a removed the tracker i18n is following a discussion, but doesn't require resolution. label Nov 20, 2019
@r12a r12a closed this as completed Nov 21, 2019
@r12a r12a added the t:typ_misc 8.7 Miscellaneous label Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
close? The related issue was closed by the Group but open here needs-resolution i18n expects this item to be resolved to their satisfaction. s:utr53 t:typ_misc 8.7 Miscellaneous
Projects
None yet
Development

No branches or pull requests

2 participants