From 0308ff86522acfefb94fc7e70ec1cdce353c5a70 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Fri, 25 Aug 2000 17:29:35 +0000 Subject: Add reference to RFC 2396 in "See also" section. Minor cleanups. --- Doc/lib/liburlparse.tex | 17 +++++++++++------ 1 file changed, 11 insertions(+), 6 deletions(-) diff --git a/Doc/lib/liburlparse.tex b/Doc/lib/liburlparse.tex index 6173fcc..ed649d1 100644 --- a/Doc/lib/liburlparse.tex +++ b/Doc/lib/liburlparse.tex @@ -1,5 +1,5 @@ \section{\module{urlparse} --- - Parse URLs into components.} + Parse URLs into components} \declaremodule{standard}{urlparse} \modulesynopsis{Parse URLs into components.} @@ -11,10 +11,11 @@ \indexii{relative}{URL} -This module defines a standard interface to break URL strings up in -components (addressing scheme, network location, path etc.), to combine -the components back into a URL string, and to convert a ``relative -URL'' to an absolute URL given a ``base URL.'' +This module defines a standard interface to break Uniform Resource +Locator (URL) strings up in components (addressing scheme, network +location, path etc.), to combine the components back into a URL +string, and to convert a ``relative URL'' to an absolute URL given a +``base URL.'' The module has been designed to match the Internet RFC on Relative Uniform Resource Locators (and discovered a bug in an earlier @@ -80,7 +81,7 @@ yields the string \begin{verbatim} 'http://www.cwi.nl/%7Eguido/FAQ.html' \end{verbatim} -% + The \var{allow_fragments} argument has the same meaning as for \code{urlparse()}. \end{funcdesc} @@ -95,4 +96,8 @@ The \var{allow_fragments} argument has the same meaning as for absolute and a relative URL, including a fair normal of ``Abnormal Examples'' which govern the treatment of border cases.} + \seerfc{2396}{Uniform Resource Identifiers (URI): Generic Syntax}{ + Document describing the generic syntactic requirements for + both Uniform Resource Names (URNs) and Uniform Resource + Locators (URLs).} \end{seealso} -- cgit v0.12