.\" Modified Fri Aug 21 23:00:00 1999 by David A. Wheeler (dwheeler@dwheeler.com)
.\" Modified Tue Mar 14 2000 by David A. Wheeler (dwheeler@dwheeler.com)
.\"
-.TH URI 7 (date) "Linux man-pages (unreleased)"
+.TH uri 7 (date) "Linux man-pages (unreleased)"
.SH NAME
uri, url, urn \- uniform resource identifier (URI), including a URL or URN
.SH SYNOPSIS
devicename colons with the vertical bar ("|") in URIs, so "C:" becomes "C|".
.PP
A fragment identifier, if included, refers to a particular named portion
-(fragment) of a resource; text after a \(aq#\(aq identifies the fragment.
-A URI beginning with \(aq#\(aq refers to that fragment in the current resource.
+(fragment) of a resource; text after a \[aq]#\[aq] identifies the fragment.
+A URI beginning with \[aq]#\[aq] refers to that fragment in the current resource.
.SS Usage
There are many different URI schemes, each with specific
additional rules and meanings, but they are intentionally made to be
a comma-separated list of type=value
pairs, where the =value portion may be omitted for options not
requiring it.
-An extension prefixed with a \(aq!\(aq is critical
+An extension prefixed with a \[aq]!\[aq] is critical
(must be supported to be valid), otherwise it is noncritical (optional).
.PP
LDAP queries are easiest to explain by example.
.IP
.in +4n
.EX
-\- _ . ! \(ti * ' ( )
+\- _ . ! \[ti] * ' ( )
.EE
.in
.PP
Unreserved characters can be escaped without changing the semantics
of the URI, but this should not be done unless the URI is being used
in a context that does not allow the unescaped character to appear.
-For example, "%7e" is sometimes used instead of "\(ti" in an HTTP URL
+For example, "%7e" is sometimes used instead of "\[ti]" in an HTTP URL
path, but the two are equivalent for an HTTP URL.
.PP
For URIs which must handle characters outside the US ASCII character set,
IETF RFC\~3986 (last paragraph of section 2.5)
recommend the following approach:
.IP (1) 5
-translate the character sequences into UTF-8 (IETF RFC\~3629)\(emsee
-.BR utf\-8 (7)\(emand
+translate the character sequences into UTF-8 (IETF RFC\~3629)\[em]see
+.BR utf\-8 (7)\[em]and
then
.IP (2)
use the URI escaping mechanism, that is,