RFC 1866 does not define any "URI encoding". It defines HTML 2.0 that

includes SGML numerical character references (&#nnn;) and entity
references (&foo;) for Added Latin 1 and a subset of Numeric and
Special Graphic.
This commit is contained in:
uwe 2012-12-15 02:08:13 +00:00
parent 6e92cc1004
commit dafbf6787b
2 changed files with 5 additions and 4 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: unvis.3,v 1.24 2012/12/15 01:50:06 uwe Exp $
.\" $NetBSD: unvis.3,v 1.25 2012/12/15 02:08:13 uwe Exp $
.\"
.\" Copyright (c) 1989, 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -162,7 +162,8 @@ will decode URI strings as specified in RFC 1808.
If set to
.Dv VIS_HTTP1866 ,
.Fn unvis
will decode URI strings as specified in RFC 1866.
will decode entity references and numeric character references
as specified in RFC 1866.
If set to
.Dv VIS_MIMESTYLE ,
.Fn unvis

View File

@ -1,4 +1,4 @@
.\" $NetBSD: unvis.1,v 1.9 2010/11/28 01:33:37 wiz Exp $
.\" $NetBSD: unvis.1,v 1.10 2012/12/15 02:08:13 uwe Exp $
.\"
.\" Copyright (c) 1989, 1990, 1993
.\" The Regents of the University of California. All rights reserved.
@ -52,7 +52,7 @@ The options are as follows:
.It Fl e
Don't decode \e escaped sequences.
.It Fl H
Decode using the URI encoding from RFC 1866.
Decode entity references and numeric character references from RFC 1866.
.Pq Dv VIS_HTTP1866
.It Fl h
Decode using the URI encoding from RFC 1808.