summaryrefslogtreecommitdiff
path: root/docs/ref/unicode.txt
diff options
context:
space:
mode:
authorMariusz Felisiak <felisiak.mariusz@gmail.com>2020-04-15 13:11:13 +0200
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2020-04-15 18:31:30 +0200
commitf1a808a5025b63715d1034af2b96a6a5241d29e9 (patch)
treedee468400b97faa9926a8f80be9d400fab2c6d85 /docs/ref/unicode.txt
parent71c4fb7beb8e3293243140e4bd74e53989196440 (diff)
Used :rfc: role in various docs.
Diffstat (limited to 'docs/ref/unicode.txt')
-rw-r--r--docs/ref/unicode.txt10
1 files changed, 4 insertions, 6 deletions
diff --git a/docs/ref/unicode.txt b/docs/ref/unicode.txt
index 2c69d669b0..e980147f49 100644
--- a/docs/ref/unicode.txt
+++ b/docs/ref/unicode.txt
@@ -143,11 +143,12 @@ from then on, you can treat the result as always being a string.
URI and IRI handling
~~~~~~~~~~~~~~~~~~~~
-Web frameworks have to deal with URLs (which are a type of IRI_). One
+Web frameworks have to deal with URLs (which are a type of IRI). One
requirement of URLs is that they are encoded using only ASCII characters.
However, in an international environment, you might need to construct a
-URL from an IRI_ -- very loosely speaking, a URI_ that can contain Unicode
-characters. Use these functions for quoting and converting an IRI to a URI:
+URL from an :rfc:`IRI <3987>` -- very loosely speaking, a :rfc:`URI <2396>`
+that can contain Unicode characters. Use these functions for quoting and
+converting an IRI to a URI:
* The :func:`django.utils.encoding.iri_to_uri()` function, which implements the
conversion from IRI to URI as required by :rfc:`3987#section-3.1`.
@@ -213,9 +214,6 @@ following is always true::
So you can safely call it multiple times on the same URI/IRI without risking
double-quoting problems.
-.. _URI: https://www.ietf.org/rfc/rfc2396.txt
-.. _IRI: https://www.ietf.org/rfc/rfc3987.txt
-
Models
======