From 19c9224cfdebfd6e7ba8d13cb7e0c974bd4ac71f Mon Sep 17 00:00:00 2001 From: Casey Duncan Date: Thu, 2 Dec 2010 23:15:36 -0700 Subject: change For example to As an example --- docs/narr/views.rst | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) (limited to 'docs') diff --git a/docs/narr/views.rst b/docs/narr/views.rst index 29adc5f14..cecba9f7a 100644 --- a/docs/narr/views.rst +++ b/docs/narr/views.rst @@ -1030,16 +1030,15 @@ via the ``request.params``, ``request.GET``, or ``request.POST`` 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 + 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. + +As an 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: -- cgit v1.2.3