[rfc-i] RFC Series publishes first RFC with non-ASCII characters

Henrik Levkowetz henrik at levkowetz.com
Tue Oct 24 07:41:58 PDT 2017

Hi Julian,

On 2017-10-24 15:29, Julian Reschke wrote:
> On 2017-09-22 18:54, Heather Flanagan (RFC Series Editor) wrote:
>> ...
>> That's an excellent question. I think this is something to discuss with
>> both the IESG and the Tools Team, though I am fairly confident that
>> "right now" isn't possible. An idnits update is one of the tools
>> contracted for, and is not yet complete (see the expected timeline here:
>> https://trac.tools.ietf.org/tools/ietfdb/wiki/FormatToolsPlan). Also,
>  > ...
> Currently says "End of January". Note that all I'm asking for is a way 
> to disable the "all ASCII" check.

It should be feasible to tweak the current idnits in this respect -- but
that's going to permit non-ascii in a lot of places where the exact rules
would not permit non-ascii.  Better checks will still have to wait for the
new idnits.

>> we've seen that the datatracker isn't rendering non-ASCII characters
>> correctly in the PDF automatically generated from RFC 8187
>> (https://trac.tools.ietf.org/tools/ietfdb/ticket/2370). So, there is
>> still some work to do before this will all work.
> FWIW, this is not about the PDF (which is fine), but the fact that 
> datatrackers's TXT-to-HTML conversion doesn't work properly (in contract 
> to the one used for the HTML on tools.ietf.org).
> It would be awesome to see some progress here.

It's on my to-do list, but not at the very top.  Will see what I can do.

Best regards,


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20171024/53db6451/attachment.asc>

More information about the rfc-interest mailing list