Stéphane Bortzmeyer <bortzmeyer at nic dot fr> wrote:
In fact, draft-4646bis makes no provision for "optional" hex NCRs, only UTF-8.Thanks for the reminding. My tool currently converts the NCR to Unicode. Should I stop?
A tool that is intended to check the Registry for conformance to the spec should stop.
A tool that is intended for practical use in language tagging might choose to be robust and continue to interpret hex NCRs, so it will work with both old and new versions of the Registry. This would backfire if a subtag were added with a Description or Comments field containing a sequence that looked like a hex NCR, which would be a supremely bad idea.
-- 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 at ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.