summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris McDonough <chrism@agendaless.com>2009-04-11 18:39:43 +0000
committerChris McDonough <chrism@agendaless.com>2009-04-11 18:39:43 +0000
commit0771d9ff0596e2b52d153253d512bea2a0bc54ef (patch)
tree542cb6910e1ff9cbdbc127c9a5eb2a4646402376
parent77a146c26fab9594b4a401fc44f1ee5b8373bbea (diff)
downloadpyramid-0771d9ff0596e2b52d153253d512bea2a0bc54ef.tar.gz
pyramid-0771d9ff0596e2b52d153253d512bea2a0bc54ef.tar.bz2
pyramid-0771d9ff0596e2b52d153253d512bea2a0bc54ef.zip
Rendering.
-rw-r--r--docs/narr/views.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/narr/views.rst b/docs/narr/views.rst
index f52b0619b..88e062abb 100644
--- a/docs/narr/views.rst
+++ b/docs/narr/views.rst
@@ -599,16 +599,16 @@ the most common encoding used on the web for non-ASCII character data,
and because working and storing Unicode values is much saner than
working with an storing bytestrings, :mod:`repoze.bfg` configures the
:term:`WebOb` request machinery to attempt to decode form submission
-values into Unicode automatically from the UTF-8 character set
-implicitly. This implicit decoding happens when view code obtains
-form field values via the :term:`WebOb` ``request.params``,
-``request.GET``, or ``request.POST`` APIs.
+values into Unicode from the UTF-8 character set implicitly. This
+implicit decoding happens when view code obtains form field values via
+the :term:`WebOb` ``request.params``, ``request.GET``, or
+``request.POST`` APIs.
For example, let's assume that the following form page is served up to
a browser client, and its ``action`` points at some :mod:`repoze.bfg`
-view code::
+view code:
-.. code-block: xml
+.. code-block:: xml
<html xmlns="http://www.w3.org/1999/xhtml">
<head>