diff options
| author | Casey Duncan <casey.duncan@gmail.com> | 2010-12-02 23:13:16 -0700 |
|---|---|---|
| committer | Casey Duncan <casey.duncan@gmail.com> | 2010-12-02 23:13:16 -0700 |
| commit | 150a32920d364fdd2de0f4005dd5fb995cba7692 (patch) | |
| tree | 61bcf42e23e755ae952bb40c3dc802380386e124 /docs | |
| parent | f5da86dfe5f4edfa443182bc6f6009e44f001d9e (diff) | |
| download | pyramid-150a32920d364fdd2de0f4005dd5fb995cba7692.tar.gz pyramid-150a32920d364fdd2de0f4005dd5fb995cba7692.tar.bz2 pyramid-150a32920d364fdd2de0f4005dd5fb995cba7692.zip | |
add note explaining the difference between Unicode and UTF-8
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/narr/views.rst | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/docs/narr/views.rst b/docs/narr/views.rst index 3cd4154fa..29adc5f14 100644 --- a/docs/narr/views.rst +++ b/docs/narr/views.rst @@ -1028,6 +1028,17 @@ This implicit decoding happens when view code obtains form field values via the ``request.params``, ``request.GET``, or ``request.POST`` APIs (see :ref:`request_module` for details about these APIs). +.. note:: + Many people find the difference between Unicode and UTF-8 confusing. + Unicode is a standard for representing text that supports most of + the world's writing systems. However, there are many ways that Unicode + data can be encoded into bytes for transmittal and storage. UTF-8 + is a specific encoding for Unicode, that is backwards-compatible + with ASCII. This makes UTF-8 very convenient for encoding data + where a large subset of that data is ASCII characters, which is + largely true on the web. UTF-8 is also the standard character + encoding for URLs. + For example, let's assume that the following form page is served up to a browser client, and its ``action`` points at some :app:`Pyramid` view code: |