diff options
| author | Michael Merickel <github@m.merickel.org> | 2018-11-20 13:40:48 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-11-20 13:40:48 -0600 |
| commit | 6918b285ba2db917b640a0d715bc70fecfd2fabe (patch) | |
| tree | 00c9160a2f9ac1d8a50bdc8ab28088e3a7aa3c82 /docs/narr/views.rst | |
| parent | 8c943501e87bed7836bb9ec1b216a561cc3f6be6 (diff) | |
| parent | b1c500c3d4cb269aed254742501040c1c64367c2 (diff) | |
| download | pyramid-6918b285ba2db917b640a0d715bc70fecfd2fabe.tar.gz pyramid-6918b285ba2db917b640a0d715bc70fecfd2fabe.tar.bz2 pyramid-6918b285ba2db917b640a0d715bc70fecfd2fabe.zip | |
Merge pull request #7 from stevepiercy/drop-py2
miscellaneous grammar and syntax fixes
Diffstat (limited to 'docs/narr/views.rst')
| -rw-r--r-- | docs/narr/views.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/narr/views.rst b/docs/narr/views.rst index 40717c37a..1b4118b85 100644 --- a/docs/narr/views.rst +++ b/docs/narr/views.rst @@ -469,7 +469,7 @@ For implicit decoding to work reliably, you should ensure that every form you render that posts to a :app:`Pyramid` view explicitly defines a charset encoding of UTF-8. This can be done via a response that has a ``;charset=UTF-8`` in its ``Content-Type`` header; or, as in the form above, -with a ``accept-charset`` tag that implies that informs the browser that the +with an ``accept-charset`` attribute, informing the browser that the server expects the form content to be encoded using UTF-8. This must be done explicitly because all known browser clients assume that they should encode form data in the same character set implied by the ``Content-Type`` value of |