diff options
| author | Steve Piercy <web@stevepiercy.com> | 2018-11-20 00:59:57 -0800 |
|---|---|---|
| committer | Steve Piercy <web@stevepiercy.com> | 2018-11-20 00:59:57 -0800 |
| commit | 9eec98980d17fee7c27aa1b36a0b8ae74b081e26 (patch) | |
| tree | 3b8ffec19f12cd2d9a6eb06b845b0b621708fa73 /docs/narr/views.rst | |
| parent | 1007fa3773a311a72dd7b2e5e8c52584c5d6e416 (diff) | |
| download | pyramid-9eec98980d17fee7c27aa1b36a0b8ae74b081e26.tar.gz pyramid-9eec98980d17fee7c27aa1b36a0b8ae74b081e26.tar.bz2 pyramid-9eec98980d17fee7c27aa1b36a0b8ae74b081e26.zip | |
grammar 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 |