W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2022

Re: support for non-ASCII in strings, was: signatures vs sf-date

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Fri, 02 Dec 2022 13:13:50 +0000
Message-Id: <202212021313.2B2DDoGH005859@critter.freebsd.dk>
To: Julian Reschke <julian.reschke@gmx.de>
cc: ietf-http-wg@w3.org
--------
Julian Reschke writes:

> >>> And if the RFC7807-crew, of all crews, did not adopt RFC5987, why
> >>> would should we expect /anybody/ to pick up standard N+1 from sfbis ?
> >>
> >> Because it would be an integral part of SF, not something added on top.
> >
> > ... but if you are trying to co-opt sfbis for your pet issue of putting  I18N
>
> So you call support for non-ASCII characters "my pet issue"?

Yes, that is the clear impression I get, both from todays and many previous discussions.

Poul-Henning

-- 
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 Friday, 2 December 2022 13:14:03 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:44:08 UTC