- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 01 May 2012 10:09:25 +0200
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- CC: Larry Masinter <masinter@adobe.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, Marcos Caceres <w3c@marcosc.com>, Doug Schepers <schepers@w3.org>, "spec-prod@w3.org" <spec-prod@w3.org>
On 2012-05-01 02:02, Leif Halvard Silli wrote: > ... > There are text encoding problems with the current RFC system too. > > First there is the problems related to describing characters, rather > than typing them directly, which makes the RFCs difficult to understand > for instance if the character describes a non-ASCII letter instead of > rendering it. Or, the problem related to descriptions such as 'below I > type an 'a', but you should consider that it is 'exotic letter x'. > ... We know. See rfc-interest mailing list. > Second, you do have encoding problems now as well. Take RFC2557, which > contains at least one non-ASCII letter - É. We know. See rfc-interest mailing list. > *<http://www.rfc-editor.org/rfc/rfc2557.txt > includes the É because the file is served as ISO-8859-1 > *<http://tools.ietf.org/html/rfc2557#section-9.1> is served, via > HTTP, with the charset label 'latin-1', which is an invalid > label, which means that the page is only correct in Web browsers > that default to Windows-1252. As far as I can tell, it's served as UTF-8. > *<http://www.rfc-editor.org/rfc/pdfrfc/rfc2557.txt.pdf> > includes the É, for some reason. > *<http://datatracker.ietf.org/doc/rfc2557/?include_text=1> > is served with the label UTF-8, but the É letter is still lost > > It seems going for UTF-8 everywhere would be simpler. We know. > ... Proposal: people who are indeed interested in the RFC format should join the rfc-interest mailing list (and look at the mailing list archives). Best regards, Julian
Received on Tuesday, 1 May 2012 08:09:56 UTC