-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Unicode combining characters treated individually when editing #2942
Comments
These combined characters break formatting when used in edited text. The formatting or references after these characters are moved when text with the combining character is loaded into the Quill editor.
is incorrectly displayed. Link start on letter i not l. The character č has normal representation č (one UTF character) but from some reason some one copied text from external source and insert it into page with Quill editor. The external editor used this strange form which broke formatting of text. |
@david-jezek Sorry it's been a while since I was actively working around Quill stuff like this but re.
You might be able to hook into Quill's paste event handlers and intercept in a way to call |
Quill 2.0 has been released (announcement post) with many changes and fixes. If this is still an issue please create a new issue after reviewing our updated Contributing guide 🙏 |
Starting at the end of a piece of text like
diacriticism
In a native macOS text control, it takes me 12 backspace presses to get rid of all the letters of the word. With Quill, it takes tons more, as it deletes each underlying code point one at a time.
To be fair… :-)
a) This is an extreme example (taken from http://demo.danielmclaren.com/2015/diacriticism/ via https://stackoverflow.com/a/51004127/179583) but could come up at a smaller scale when editing languages that use e.g. diacritical marks above letters for which there are no pre-composed characters. [Haven't tested if Quill normalizes characters to pre-composed for at least the cases where there are such characters.]
b) I also noticed that neither Chrome nor Firefox themselves handle this well either (!!), so I suspect they must have also implemented their own text handling themselves in a similar way as Quill did.
Flagging this for potential future enhancement at some point, or if it's indicative of related Unicode handling issues (xref #1230).
The text was updated successfully, but these errors were encountered: