test_wsgirequest_charset: Use UTF-8 instead of iso-8859-1test_wsgirequest_charset_use_UTF-8_instead_of_iso-8859-1

because it seems that the defacto standard for encoding URIs is to use UTF-8.

I've been reading about url encoding and it seems like perhaps using an
encoding other than UTF-8 is very non-standard and not well-supported (this
test is trying to use `iso-8859-1`).

From http://en.wikipedia.org/wiki/Percent-encoding

> For a non-ASCII character, it is typically converted to its byte sequence in
> UTF-8, and then each byte value is represented as above.

> The generic URI syntax mandates that new URI schemes that provide for the
> representation of character data in a URI must, in effect, represent
> characters from the unreserved set without translation, and should convert
> all other characters to bytes according to UTF-8, and then percent-encode
> those values. This requirement was introduced in January 2005 with the
> publication of RFC 3986

From http://tools.ietf.org/html/rfc3986:

> Non-ASCII characters must first be encoded according to UTF-8 [STD63], and
> then each octet of the corresponding UTF-8 sequence must be percent-encoded
> to be represented as URI characters.  URI producing applications must not use
> percent-encoding in host unless it is used to represent a UTF-8 character
> sequence.

From http://tools.ietf.org/html/rfc3987:

> Conversions from URIs to IRIs MUST NOT use any character encoding other than
> UTF-8 in steps 3 and 4, even if it might be possible to guess from the
> context that another character encoding than UTF-8 was used in the URI.  For
> example, the URI "http://www.example.org/r%E9sum%E9.html" might with some
> guessing be interpreted to contain two e-acute characters encoded as
> iso-8859-1. It must not be converted to an IRI containing these e-acute
> characters.  Otherwise, in the future the IRI will be mapped to
> "http://www.example.org/r%C3%A9sum%C3%A9.html", which is a different URI from
> "http://www.example.org/r%E9sum%E9.html".

See issue #7, which I think this at least partially fixes.

1 files changed, 69 insertions, 0 deletions

diff --git a/docs/web/site.js b/docs/web/site.js
new file mode 100644
index 0000000..ed23575
--- /dev/null
+++ b/docs/web/site.js
@@ -0,0 +1,69 @@
+function setup_dropdowns() {
+  var els = document.getElementsByTagName('UL');
+  for (var i = 0; i < els.length; i++) {
+    var el = els[i];
+    if (el.className.search(/\bcontents\b/) > -1) {
+      enable_dropdown(el);
+    }
+  }
+}
+
+function enable_dropdown(el) {
+  var title = el.getElementsByTagName('LI')[0];
+  var plus_minus = document.createTextNode('  [-]');
+  if (title.childNodes[0].tagName != 'A') {
+    anchor = document.createElement('A');
+    while (title.childNodes.length) {
+      anchor.appendChild(title.childNodes[0]);
+    }
+    anchor.setAttribute('href', '#');
+    anchor.style.padding = '1px';
+    title.appendChild(anchor);
+  } else {
+    anchor = title.childNodes[0];
+  }
+  anchor.appendChild(plus_minus);
+  function show_hide() {
+    if (el.sub_hidden) {
+      set_sub_li(el, '');
+      anchor.removeChild(plus_minus);
+      plus_minus = document.createTextNode('  [-]');
+      anchor.appendChild(plus_minus);
+    } else {
+      set_sub_li(el, 'none');
+      anchor.removeChild(plus_minus);
+      plus_minus = document.createTextNode('  [+]');
+      anchor.appendChild(plus_minus);
+    }
+    el.sub_hidden = ! el.sub_hidden;
+    return false;
+  }
+  anchor.onclick = show_hide;
+  show_hide();
+}
+
+function set_sub_li(list, display) {
+  var sub = list.getElementsByTagName('LI');
+  for (var i = 1; i < sub.length; i++) {
+    sub[i].style.display = display;
+  }
+}
+
+function add_onload(func) {
+  if (window.onload) {
+    var old_onload = window.onload;
+    function new_onload() {
+      old_onload();
+      func();
+    }
+    window.onload = new_onload;
+  } else {
+    window.onload = func;
+  }
+}
+
+add_onload(setup_dropdowns);
+
+      
+
+