Re: RFC Series publishes first RFC with non-ASCII characters

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ohta-san,

On Sun, Sep 17, 2017 at 04:59:44AM +0900, Masataka Ohta wrote:
> Lyndon Nerenberg wrote:
> 
> >> which means RFCs should be pure ASCII just as programming languages
> >> use pure ASCII.
> > 
> > Plan 9's C compilers have supported UTF8 in the grammar for decades.
> 
> You still don't understand the problem at all.

If that is the case (which I neither confirm nor deny), then you should
provide a more detailed explanation of the problem, rather than
just repeating your previous statement.

> As I wrote:
> 
>  >>> environment has difficulty in handling non-ASCII characters.
>  >>
>  >> That's not a problem.
> 
> lack of implementations to support a bad idea is not a problem.
> 
> As such, providing such implementations is not a solution.
> 
> With reasons, C, as standardized by ISO, use pure ASCII.
> 
> If a really international team of programmers must tightly
> cooperate using Plan 9 C compiler, code must be written using
> limited set of characters recognized by all the members.

Furthermore, you seem to be repeatedly making assertions of how
things must be, without providing any supporting justifciation
for those assertions.  This does not help us have a productive
discussion; it seems rather likely to instead lead to frustration
on all sides, including the passive readership of this list.

-Ben




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]