On Wed, Nov 03, 2021 at 11:11:00AM +0100, Marc-Andre Lemburg wrote:
Coming back to the thread topic, many of the Unicode security considerations don't apply to non-Unicode encodings, since those usually don't support e.g. changing the bidi direction within a stream of text or other interesting features you have in Unicode such as combining code points, invisible (space) code points, font rendering hint code points, etc.
So in a sense, those non-Unicode encodings are safer than using UTF-8 :-)
Thank you MAL for that timely reminder that most encodings are not Unicode. I have to admit that I often forget that there is a whole universe of non-Unicode, non-ASCII encodings.
Please also note that most character lookalikes are not encoding issues, but instead font issues, which then result in the characters looking similar.
+1 -- Steve