Fix incorrect term "Absolute URL" throughout documentation

[sharan666]

Returns an absolute URL (i.e., a URL without the domain name

should read

Returns an relative URL (i.e., a URL without the domain name

[Tim Graham]

Looks like this is on docs/ref/templates/builtins.txt

[Chris Beaven]

Even though this is technically correct and Django is in the wrong (​http://tools.ietf.org/html/rfc1808), having methods like get_absolute_url() which do the same thing show that the meaning in the documentation is "absolute URL".

A happy medium may be to call it an "absolute URL path"

In any case, fixing this isn't just fixing a minor error in one place, there are references all over the place which should use consistent language:

./faq/usage.txt:       called ``mug_shot``, you can get the absolute URL to your image in a
./intro/tutorial03.txt:All the poll app cares about is its relative URLs, not its absolute URLs.
./topics/auth.txt:          default), passing the current absolute URL in the query string as
./ref/request-response.txt:    absolute URL with no domain (e.g. ``'/search/'``). Note that this returns
./ref/models/instances.txt:In this way, you're tying the model's absolute URL to the view that is used
./ref/models/fields.txt:       you can get the absolute URL to your image in a template with
./ref/templates/builtins.txt:Returns an absolute URL (i.e., a URL without the domain name) matching a given
./ref/contrib/syndication.txt:The :attr:`link` method/attribute can return either an absolute URL (e.g.
./ref/contrib/sitemaps.txt:        If it's a method, it should return the absolute URL for a given object as
./ref/contrib/sitemaps.txt:        If it's an attribute, its value should be a string representing an absolute URL
./ref/contrib/sitemaps.txt:        In both cases, "absolute URL" means a URL that doesn't include the protocol or
./ref/contrib/sitemaps.txt:    which should be the absolute URL of your site's sitemap (e.g.,

[Malcolm Tredinnick]

We should definitely fix it and use the phrase "absolute path reference" (possibly abbreviated to "absolute path" after frequent use). That is the term used in RFC 2396, which is the URI spec. The current Django usage has always annoyed me and is almost certainly due to a misunderstanding when the docs were originally written. It's wrong currently; let's fix it.

By the way, we can't use the 'i.e.' phrasing of the current docs after the terms "relative URL" since it's not an "i.e.", it's an "e.g." and that isn't correct in those contexts either.

[Gabriel Hurley]

+1 for "absolute path". The current usage bugs the heck out of me too. I will start correcting these in other patches as I come across them, in addition to working on this patch.

[Gabriel Hurley]

(In [14482]) Fixed #10904 -- Corrected inappropriate usage of the term "absolute URL" throughout the docs. Replaced with the (RFC 2396-compliant) terms "absolute path reference" or "absolute path" as appropriate for the context. Thanks to sharan666 for the report, and Malcolm, Chris, and dwillis for their work in supplying a solution and patch.

[Gabriel Hurley]

(In [14483]) [1.2.X] Fixed #10904 -- Corrected inappropriate usage of the term "absolute URL" throughout the docs. Replaced with the (RFC 2396-compliant) terms "absolute path reference" or "absolute path" as appropriate for the context. Thanks to sharan666 for the report, and Malcolm, Chris, and dwillis for their work in supplying a solution and patch.

Backport of [14482] from trunk.

[Jacob]

Milestone 1.3 deleted