Guy Harris writes: > For what it's worth, we say > > The authors wish to thank: Michael Tuexen, Mohamed Boucadair, Carsten > Bormann, Henk Birkholtz, and Robert Wilton their invaluable comments > and encouragement. > > rather than "... Michael Tüxen ..." in the Acknowledgements section.
It looks like using non-ASCII characters in people's names in text RFCs began with RFC 8187 (2017), which is specifically about the subject of character encodings. It already included Unicode examples of currency symbols, and then thanked "Martin Dürst" in the acknowledgements. In recent RFCs it's not uncommon. The first RFC to include a non-ASCII character is RFC 64 which uses a µ (in an IBM-style codepage encoding, I think). But this was probably retyped later from a paper memo. Some RFCs in the 100s have annotations crediting people for digitizing them in 1999, and the credits also include single-byte non-ASCII accented charactersA After that there are some technical symbols in RFC 1305, and then only a few curly quotes (that probably escaped editors' notice!) until RFC 8187, mentioned above. The acknowledgements section of RFC 8896 thanks Jürgen Schönwälder, who has all the possible German umlauted vowels in his name! RFC 8694 has an author's name and affiliation in Chinese (with a transliteration and translation), and then the same author's postal address in Chinese (again with a translation). Likewise RFC 9005, but this practice doesn't seem to have caught on otherwise. _______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
