[Ltru] Re: draft-4645bis-03

Stéphane Bortzmeyer <bortzmeyer at nic dot fr> wrote:

> You apparently did not use the possibility of using UTF-8 in the 
> Description fields?

Regarding the I-D:  my understanding is that non-ASCII is not allowed in 
I-Ds.  This is why the data in the Registry uses NCRs and is accompanied 
by an instruction to IANA (with "MUST") to convert it to UTF-8.

I'm not 100% sure about the non-ASCII restriction; someone once said 
that only applied to RFCs, whereas the non-ASCII part of 4645bis (like 
4645 before it) will be stripped out before the draft is published as an 
RFC.  I seem to remember trying to run UTF-8 through xml2rfc and ending 
up with non-validating HTML and ASCII-mutilated text, and never trying 
it again.

In private mail, Stéphane asked me for a copy of just the proposed 
4645bis Registry, without the surrounding text, and I sent him one.  But 
at 6:50 in the morning, with normal morning family activities around me, 
my brain malfunctioned and I forgot to convert the file to UTF-8.  That 
may be what he was referring to.

In fact, draft-4646bis makes no provision for "optional" hex NCRs, only 
UTF-8.  The description "Volap&#xFC;k" would literally be 12 characters 
long, including the three non-alphabetic characters.

--
Doug Ewell  *  Fullerton, California, USA  *  RFC 4645  *  UTN #14
http://home.roadrunner.com/~dewell
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ

_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru