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

julian.reschke at gmx.de (Julian Reschke) Tue, 01 March 2016 18:47 UTC

From: julian.reschke at gmx.de (Julian Reschke)
Date: Tue, 1 Mar 2016 19:47:49 +0100
Subject: [rfc-i] draft-iab-rfc-nonascii-00
In-Reply-To: <56D5E290.1@rfc-editor.org>
References: <56D33DF2.3090600@gmx.de> <56D49206.7050407@rfc-editor.org> <56D5E290.1@rfc-editor.org>
Message-ID: <56D5E3D5.1050804@gmx.de>

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