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.

Sign up for GitHub

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

Jump to bottom

bidi algorithm (for right-to-left Unicode characters) #5853

Open
Flimm opened this issue Apr 13, 2021 · 2 comments
Open

bidi algorithm (for right-to-left Unicode characters) #5853

Flimm opened this issue Apr 13, 2021 · 2 comments
Labels
Support data suggestion

Comments

@Flimm
Copy link

Flimm commented Apr 13, 2021 •
edited
Loading

Unicode provides a bunch of characters, that are needed when using bidirectional text, that is when mixing right-to-left text with left-to-right text. Almost all languages that right-to-left text will need to mix it with left-to-right text on occasion (for example, when adding URLs or numbers).

W3C have this GitHub website that documents the support for the Unicode bidi algorithm in different browsers: https://w3c.github.io/i18n-tests/results/bidi-algorithm
@Flimm Flimm changed the title bidi algorithm bidi algorithm (for right-to-left Unicode characters) Apr 13, 2021
@Schweinepriester
Copy link
Contributor

Related:

@Flimm
Copy link
Author

Flimm commented Apr 13, 2021

Thanks @Schweinepriester . The issue #996 is about the CSS properties direction and unicode-bidi. Whereas this issue is about the support for Unicode special characters like U+202B. If you read this document explaining these special characters, it says things like:

at the time of writing browsers still don't support RLI/LRI,

It would be useful to know which browsers do support the Unicode bidi algorithm completely, including these special characters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Support data suggestion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Flimm @Fyrd @Schweinepriester