[rfc-i] draft-iab-rfc-nonascii-00

Julian Reschke julian.reschke at gmx.de
Tue Mar 1 10:47:49 PST 2016


On 2016-03-01 19:42, Heather Flanagan (RFC Series Editor) wrote:
> On 2/29/16 10:46 AM, Heather Flanagan (RFC Series Editor) wrote:
>>> "People whose system does not have the fonts needed to display a
>>>> particular RFC need to be able to read the various publication formats
>>>> and the XML correctly in order to understand and implement the
>>>> information described in the document."
>>>>
>>>> Maybe "will have to read alternative publication formats"?
>>>>
>>>> <http://greenbytes.de/tech/webdav/draft-iab-rfc-nonascii-00.html#rfc.section.3>:
>> Will fix in -02.
>>
>
> Actually, I take back the "will fix". This ties into the other thread
> regarding why we are using the "ascii" attribute at all. This text feeds
> that requirement.

Unless I'm missing something, we have the ASCII alternatives only for 
contact and reference information.

How do they help with understanding the actual specification?

Best regards, Julian



More information about the rfc-interest mailing list