- From: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Date: Thu, 13 Oct 2016 06:27:14 +0000
- To: Kari Hurtta <hurtta-ietf@elmme-mailer.org>
- cc: HTTP working group mailing list <ietf-http-wg@w3.org>
-------- In message <20161013033431.B21C413FF4@welho-filter2.welho.com>, Kari Hurtta wri tes: >How about >| UTF8-octets = *( UTF8-char ) >| UTF8-2 = %xC2-DF UTF8-tail >| UTF8-3 = %xE0 %xA0-BF UTF8-tail / %xE1-EC 2( UTF8-tail ) / >| %xED %x80-9F UTF8-tail / %xEE-EF 2( UTF8-tail ) >| UTF8-4 = %xF0 %x90-BF 2( UTF8-tail ) / %xF1-F3 3( UTF8-tail ) / >| %xF4 %x80-8F 2( UTF8-tail ) >| UTF8-tail = %x80-BF >| >| NOTE -- The authoritative definition of UTF-8 is in [UNICODE]. This >| grammar is believed to describe the same thing Unicode describes, but >| does not claim to be authoritative. Implementors are urged to rely >| on the authoritative source, rather than on this ABNF. >Are you meaining following: > >h1_unicode_utf8 = h1_utf8_1 / UTF8-2 / UTF8-3 / UTF8-4 >h1_utf8_1 = ( "\" "\" ) / > ( "\" "u" 4*HEXDIG ) / > 0x20-21 / > 0x23-5B / > 0x5D-7E / > 0x80-F7 >UTF8-2 = <UTF8-2, defined in RFC 3629, Section 4> >UTF8-3 = <UTF8-3, defined in RFC 3629, Section 4> >UTF8-4 = <UTF8-4, defined in RFC 3629, Section 4> Yes, that looks like the a way to do it. BTW: The ID lives here, pull requests are welcome: https://github.com/bsdphk/id_common_structure -- 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 Thursday, 13 October 2016 06:27:44 UTC