[tahoe-dev] [tahoe-lafs] #689: web documents should be constructed out of unicode strings

[tahoe-lafs]

#689: web documents should be constructed out of unicode strings
-------------------------------+--------------------------------------------
 Reporter:  kpreid             |           Owner:           
     Type:  enhancement        |          Status:  new      
 Priority:  minor              |       Milestone:  undecided
Component:  code-frontend-web  |         Version:  1.4.1    
 Keywords:  unicode            |   Launchpad_bug:           
-------------------------------+--------------------------------------------
 The Tahoe WUI pages are generated out of Python 'str', rather than
 'unicode' objects. This is error-prone and potentially tedious, as
 anything which embeds potentially non-ASCII text in the page must
 explicitly specify the encoding at that point; for example, render_row in
 directory.py does.

 Instead, the page content should be constructed out of Unicode strings,
 and only one point should know what the encoding is, and also be
 responsible for reporting that encoding in the Content-Type of the
 response.

 Whether this is practical depends on the design of Nevow, about which I
 know nothing.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/689>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid