Every time I look at #Unicode gotchas, I 😰:

“RFC 9839 And Bad Unicode”, Tim Bray (https://www.tbray.org/ongoing/When/202x/2025/08/14/RFC9839).

On HN: https://news.ycombinator.com/item?id=44995640

On Lobsters: https://lobste.rs/s/qrs9w8/rfc_9839_bad_unicode

#UTF #Encoding #Text #RFC #RFC9839 #Validation #ErrorHandling #UTF8

RFC 9839 and Bad Unicode

https://www.tbray.org/ongoing/When/202x/2025/08/14/RFC9839

#HackerNews #RFC9839 #BadUnicode #TechNews #InternetStandards #UnicodeIssues

«Unicode is good. If you’re designing a data structure or protocol that has text fields, they should contain #Unicode characters encoded in #UTF8. There’s another question, though: “Which Unicode characters?” The answer is “Not all of them, please exclude some.”

This issue keeps coming up, so [ @paulehoffman and @timbray ] put together an individual-submission draft to the IETF and now (where by “now” I mean “two years later”) it’s been published as #RFC9839. It explains which characters are bad, and why, then offers three plausible less-bad subsets that you might want to use.»

https://www.tbray.org/ongoing/When/202x/2025/08/14/RFC9839 by @timbray

#programming #CharacterEncoding #LML