Hellow Patrick Mevzek,

   Thanks.

   Your suggestion is very good.   RFC7997 is an informational RFC, and shows a 
direction. 
   Because the popular form of RFC is TXT, the TXT can not display non ASCII 
very well.
   I can use the natvie unicode characters in draft, but many readers will not 
display it correctly.
   According to my current understanding,  U+XXXX is still the proper way to be 
easily understood by most readers.
   Many years ago, IETF EAI WG also discussed this related issue.
   I still do not see which rfc uses the natvie unicode characters directly.

   
   If possilbe, I may suggest to add some texts in the draft, which says "in 
future, the natvie unicode characters instead of U+XXXX notation are suggested 
to use in the document"

Best Regards
Jiankang Yao

> -----原始邮件-----
> 发件人: "Patrick Mevzek" <p...@dotandco.com>
> 发送时间: 2018-11-02 12:54:37 (星期五)
> 收件人: regext@ietf.org
> 抄送: 
> 主题: [regext] draft-ietf-regext-bundling-registration and characters 
> representation
> 
> Hello,
> 
> This draft, by essence, needs and uses a lot of characters outside of ASCII 
> and for these use the U+XXXX notation.
> 
> There is now however RFC7997 (The Use of Non-ASCII Characters in RFCs) and 
> among other things it says:
> 
> - the encoding of future RFCs will be in UTF-8
> - Where the use of non-ASCII characters is purely part of an example
>    and not otherwise required for correct protocol operation, escaping
>    the non-ASCII character is not required.
> - The RFC Editor encourages the use of the U+ notation except within a
>    code component where one must follow the rules of the programming
>    language in which the code is being written.
> 
> 
> So maybe the XML examples could be rewritten by using the native unicode 
> characters
> instead of the U+ notation, as I believe it would make them far more 
> understandable.
> 
> In the text, the other recommendations of the above RFC could be applied to 
> have
> more standardized handling.
> 
> -- 
>   Patrick Mevzek
>   p...@dotandco.com
> 
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to