Post AzusThJgNkzw3LWwLI by DrHyde@fosstodon.org
 (DIR) More posts by DrHyde@fosstodon.org
 (DIR) Post #AxSHplRvQ8dy8QV7yq by publicvoit@graz.social
       2025-08-23T08:08:24Z
       
       0 likes, 0 repeats
       
       «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
       
 (DIR) Post #AxSIGWwRT5nqxUXQNE by mms@mastodon.bsd.cafe
       2025-08-23T08:13:11Z
       
       0 likes, 0 repeats
       
       @publicvoit @paulehoffman @timbray step 1. -disable emoji support
       
 (DIR) Post #AzusThJgNkzw3LWwLI by DrHyde@fosstodon.org
       2025-11-04T22:55:05Z
       
       0 likes, 0 repeats
       
       @publicvoit @paulehoffman @timbray there is still so much stuff out there and so many mis-configured systems not under your control that just plain break UTF-8 that I recommend - if you can - always encoding non-ASCII characters in ASCII. eg, in JSON use strings like "I like \u03c0 especially Greek pie".