- From: Paul Hoffman <paul.hoffman@vpnc.org>
- Date: Sat, 10 Mar 2012 12:43:43 -0800
- To: Larry Masinter <masinter@adobe.com>
- Cc: xml2rfc list <xml2rfc@ietf.org>, public-i18n-core@w3.org
On Mar 10, 2012, at 12:34 PM, Larry Masinter wrote: > Since Internet Drafts and RFCs already allow supplying and delivering PDF, we wouldn't have to change IETF policy to get these examples actually legible to those who need to read and interpret them. This is a discussion for rfc-interest, not for xml2rfc. If the RFC Editor allows putting non-ASCII characters in RFCs, it is safe to assume that the xml2rfc tool will be updated to allow that. If the RFC Editor does not allow that, it makes little sense to allow it in Internet Drafts that are intended to become RFCs. Just because you are punching from the side instead of going through the top, that doesn't change the fact that you are re-opening the can of worms. (I say this as someone who has advocated for what you want in the past, doing so with Internet Drafts, not just questions on mailing lists.) --Paul Hoffman
Received on Saturday, 10 March 2012 20:44:15 UTC