On 2025-10-27, at 21:20, Brian E Carpenter <[email protected]> wrote: > > The ability to use non-ASCII characters in RFCs in a clear and consistent > manner will allow the correct display of proper names and improve the ability > to describe internationalized protocols. Apart from their role in proper > names, non-ASCII characters should be used only when they enhance the > technical content and accuracy of the document.
What does that mean? Is the use of α and β in RFC 9438 “enhancing the technical content and accuracy of the document”? They could have written alpha and beta everywhere, replaced ≤ in RFC 9277, 9582 or 9843 by <=, etc. Same content, same accuracy, just harder to read. (Separately from this question, I still hope we can at some point get rid of the typewriterisms such as the super-ugly hyphen-minus problem, but we seem to be stuck on the typewriter.) Grüße, Carsten -- rswg mailing list -- [email protected] To unsubscribe send an email to [email protected]
