- From: Larry Masinter <masinter@adobe.com>
- Date: Sat, 10 Mar 2012 12:34:39 -0800
- To: "julian.reschke@gmx.de" <julian.reschke@gmx.de>
- CC: Russ Allbery <rra@stanford.edu>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, Martin Dürst (duerst@it.aoyama.ac.jp) <duerst@it.aoyama.ac.jp>, "Adil Allawi (adil@diwan.com)" <adil@diwan.com>, "Peter Saint-Andre (stpeter@stpeter.im)" <stpeter@stpeter.im>, Chris Weber <chris@lookout.net>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
{{Talking about allowing a conditional-use in XML2RFC where you could supply unicode strings for the .HTML and .PDF rendeirngs}}
> Maybe we should start small, and look at your concrete use case.
> I'll assume it has to do with putting non-ASCII characters into IRI examples?
Yes. There are several examples where accented roman characters I think would be more useful, especially when talking about uncoded and coded forms.
Take the first example of section 3.4.1.
For example, the IRI
"http://résumé.example.org"
will be converted to
"http://r%C3%A9sum%C3%A9.example.org".
But in fact there is no way to put "an IRI" in an Internet draft, since it is a sequence of unicode characters, and to give an example of one in an ascii-only document, you have to use an encoded form.
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.
Received on Saturday, 10 March 2012 20:35:25 UTC