- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Sat, 28 Jan 2012 08:15:19 +0000
- To: Amos Jeffries <squid3@treenet.co.nz>
- cc: ietf-http-wg@w3.org
In message <4F235884.3020905@treenet.co.nz>, Amos Jeffries writes: >On 28/01/2012 1:40 p.m., Poul-Henning Kamp wrote: >> >> I18N in transport headers: Forget it, it would kill performance if >> done right, and do nobody any good if not. >> >> I18N in content headers: Sure, be my guest. > >Skipping over I18N and its multiple charsets and going specifically to >UTF-8 representation of the existing header could be an option though. Which transport headers is it that you think need ASCII++ ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Saturday, 28 January 2012 08:15:52 UTC