Robert, This is a good point. It even applies to the IETF secretariat. It used to be impossible to register with your "real name" if it contained non-ASCII characters. I think that has changed, I recall having Seen Olafur Gudmundson's badge with the real Icelandic "curly d" (or whatever it is called in English) at a recent meeting. I have not seen Japanese or Chinese or Korean, which I guess would be the next logical step...
Ole Ole J. Jacobsen Editor and Publisher, The Internet Protocol Journal Academic Research and Technology Initiatives, Cisco Systems Tel: +1 408-527-8972 GSM: +1 415-370-4628 E-mail: [EMAIL PROTECTED] URL: http://www.cisco.com/ipj On Tue, 29 Nov 2005, Robert Sayre wrote: > I've noticed that the recent debate on the ASCII text format has often > conflated formatting of artwork and Unicode support. I think finding a > non-text artwork format that has free uniform authoring (including > diffs) and viewer support will be impossible for the next 5-10 years. > An XML equivalent to Postscript may eventually be widely implemented. > The current effort, SVG, is a massive specification, unevenly > implemented, and lacks a thorough test suite. > > Unicode support is a different matter. I find the current IETF policy > to be incredibly bigoted. Many RFCs and I-Ds are currently forced to > misspell the names of authors and contributors, which doesn't seem > like correct attribution to me. So, I recommend that the IETF > secretariat and the RFC Editor change their policies to allow UTF-8 > text files. That way, older RFCs and I-Ds produced using the current > tools would follow the same encoding. > > I'm sure someone has already suggested this approach, but I'll add my > voice to the chorus. > > Robert Sayre > > _______________________________________________ > Ietf mailing list > [email protected] > https://www1.ietf.org/mailman/listinfo/ietf > _______________________________________________ Ietf mailing list [email protected] https://www1.ietf.org/mailman/listinfo/ietf
