I've investigated a bit, and the good news is, I think this must be
pretty easy to fix, because is't *just* an issue with encodings. In
fact, the notebook seems to be unicode-safe, except for the html
serving: it's just that firefox *thinks* the html served by the
notebook is in latin-1 encoding (iso-8859-1), but it is in fact in
utf-8 encoding. Manually changing the encoding makes the page render
ok (accents and all look good).
Thus, the fix that is required is the following:
a) add a
Content-Type: text/html; charset=utf-8
header to the HTTP response given by twisted. This is probably the
best and easier to implement --- I just couldn't find where to do it
in the notebook source, but it must be easy for someone familiar with
notebook code.
b) alternatively, add a line
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
to the <head> section of every page served by the notebook. This I
could do by changing templates and search&replace in the notebook
source, etc... I wouldn't be sure to catch all instances, and in
general I think (a) is preferrable.
Gonzalo
#5564 fixes a problem where one could enter "complicated" UTF-8 text
(Asian languages are most problematic) and get it to display -- but when
one double-clicked on the cell to edit, the text would get garbled.
Dan
--
--- Dan Drake <dr...@kaist.edu>
----- KAIST Department of Mathematical Sciences
------- http://mathsci.kaist.ac.kr/~drake