Opened at 2009-05-01T20:40:16Z
Last modified at 2010-05-11T16:01:17Z
#689 new enhancement
web documents should be constructed out of unicode strings
| Reported by: | kpreid | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | eventually |
| Component: | code-frontend-web | Version: | 1.4.1 |
| Keywords: | unicode | Cc: | kpreid |
| Launchpad Bug: |
Description
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.
Change History (3)
comment:1 Changed at 2009-06-19T21:51:24Z by kpreid
- Cc kpreid added
comment:2 Changed at 2010-02-02T00:22:10Z by davidsarah
- Milestone changed from undecided to 1.7.0
comment:3 Changed at 2010-05-11T16:01:17Z by zooko
- Milestone changed from 1.7.0 to eventually
Note: See
TracTickets for help on using
tickets.
It's desirable to fix this in the same milestone as the other main Unicode tickets: #534, #565 and #731.