Why GNU moe does not use UTF-8 or other form of Unicode?

Re:Why GNU moe does not use UTF-8 or other form of Unicode? by duped on Wednesday January 19, 2022 @01:40AM (#29990688)

Parsing UTF-8 is not much harder than parsing ASCII unless you're doing something weird like relying on codepoint indices for absolute file locations, which is great for a toy and really weak design for a production parser.

[ Parent | on HN ]

Re:Why GNU moe does not use UTF-8 or other form of Unicode? by rurban on Wednesday January 19, 2022 @02:11AM (#29990844)

So why nobody is doing it right then, still?

Everybody is prone to Unicode confusables attacks, and almost nobody checks for invalid chars. Almost nobody can search Unicode strings, almost nobody implemented identifiable identifiers.

[ Parent | on HN ]

Re:Why GNU moe does not use UTF-8 or other form of Unicode? by wruza on Wednesday January 19, 2022 @04:35AM (#29991617)

What could be a correct counter argument to this?

[ Parent | on HN ]

Re:Why GNU moe does not use UTF-8 or other form of Unicode? by vintermann on Wednesday January 19, 2022 @06:14AM (#29992254)

I don't know, but not going back to ISO-8859-15, that's for sure.

[ Parent | on HN ]

Re:Why GNU moe does not use UTF-8 or other form of Unicode? by rurban on Friday January 21, 2022 @01:04AM (#30019780)

Fix the implementations.

[ Parent | on HN ]