> On 31. Aug 2025, at 20:40, Guy Harris <[email protected]> wrote: > > On Aug 31, 2025, at 10:11 AM, Michael Tuexen > <[email protected]> wrote: > >> On 30. Aug 2025, at 23:35, Guy Harris <[email protected]> wrote: >> >>> Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: >>> ---------------------------------------------------------------------------- >>> >>> == There are 2 instances of lines with non-ascii characters in the document. >>> >>> Both are from ü from "Tüxen, M.", as per the above. >> Hi Guy, >> >> please just ignore them... I always have this. I changed using Tuexen on >> Tüxen >> by advice from the RFC editor a long time ago. > > If the RFC editor told you to use Tüxen, that sounds like official policy. > (RFC 7997 is "Informative", but it still approves of UTF-8.) Maybe "told me" is too strong, but they said something like "you can now use Tüxen and we would like to try it"... Something like that. Since then I use Tüxen and when checking NITs, I always ignore the report. I have had never problems related to that during the processing of the document by by RFC editor. > > Given that, I don't know what version of idnits allows them (and, presumably, > checks to make sure octets with the high bit set are *only* used in valid > UTF-8 sequences); if that's idnits 2 rather than the not-yet-released idnits > 3, perhaps idnits 2 should be used. > > In any case, I'll ignore it. Yes, please. > > Should I change all acknowledgments of "Michael Tuexen" t be "Michael Tüxen"? Michael Tüxen...
Sorry for any inconvenience related to the fact that not everybody's name only uses ASCII characters... Best regards Michael _______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
