--- a/doc/whatsnew-0.8.txt	Fri Nov 12 04:07:05 2004 +0000
+++ b/doc/whatsnew-0.8.txt	Fri Nov 12 04:27:00 2004 +0000
@@ -28,8 +28,8 @@
 information about how this is done.
 
 
-Added support for HTTP charset selection
-========================================
+8-bit character set support in Web interface
+============================================
 
 XXX This doesn't appear in the main documentation
 
@@ -42,6 +42,32 @@
 In both cases, the value is a valid charset name (eg. ``utf-8`` or
 ``kio8-r``).
 
+Inside Roundup, all strings are stored and processed in utf-8.
+Unfortunately, some older browsers do not work properly with
+utf8-encoded pages (e.g. Netscape Navigator 4 displays wrong
+characters in form fields).  This version allows to change
+the character set for http transfers.  To do so, you may add
+the following code to your ``page.html`` template::
+
+ <tal:block define="uri string:${request/base}${request/env/PATH_INFO}">
+  <a tal:attributes="href python:request.indexargs_href(uri,
+   {'@charset':'utf-8'})">utf-8</a>
+  <a tal:attributes="href python:request.indexargs_href(uri,
+   {'@charset':'koi8-r'})">koi8-r</a>
+ </tal:block>
+
+(substitute ``koi8-r`` with appropriate charset for your language).
+Charset preference is kept in the browser cookie ``roundup_charset``.
+
+Lines ``meta http-equiv`` added to the tracker templates in version 0.6.0
+should be changed to include actual character set name::
+
+ <meta http-equiv="Content-Type"
+  tal:attributes="content string:text/html;; charset=${request/client/charset}"
+ />
+
+Actual charset is also sent in the http header.
+
 
 Web Interface Miscellanea
 =========================