All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

RFC 9839: Defining Safer Unicode Character Subsets for Protocols and Data Structures

By

Bogdanp

9mo ago· 7 min readenInsight

Summary

RFC 9839 addresses the issue of which Unicode characters should be excluded from text fields in data structures and protocols, despite Unicode being generally beneficial. The authors explain why certain characters are problematic and propose three practical subsets for safer implementation.

Key quotes

· 3 pulled
Unicode is good. If you're designing a data structure or protocol that has text fields, they should contain Unicode characters encoded in UTF-8.
There's another question, though: 'Which Unicode characters?' The answer is 'Not all of them, please exclude some.'
It explains which characters are bad, and why, then offers three plausible less-bad subsets that you might want to use.
Snippet from the RSS feed
Unicode is good. If you’re designing a data structure or protocol that has text fields, they should contain Unicode characters encoded in UTF-8. There’s another question, though: “Which Unicode characters?” The answer is “Not all of them, ple

You might also wanna read