Modify ↓
Opened 15 years ago
Closed 15 years ago
#8852 closed defect (duplicate)
Non Ascii characters in Trac
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | highest | Milestone: | |
Component: | database backend | Version: | none |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
My trac shows this error when trying to view Active Tickets report. This is maybe because i entered "non Ascii" characters in a new ticket with MYSQL dbin the backend. Please suggest a way around as all my tickets are going to include japanese characters. Is there a way to enter raw characters?? For the ticket in my trac, i translated english-japanese via google.
Traceback (most recent call last): File "C:\Python25\Lib\site-packages\trac\web\main.py", line 423, in _dispatch_request dispatcher.dispatch(req) File "C:\Python25\Lib\site-packages\trac\web\main.py", line 197, in dispatch resp = chosen_handler.process_request(req) File "C:\Python25\Lib\site-packages\trac\ticket\report.py", line 105, in process_request template, data, content_type = self._render_view(req, db, id) File "C:\Python25\Lib\site-packages\trac\ticket\report.py", line 409, in _render_view value = unicode(result[col_idx])
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe3 in position 1: ordinal not in range(128)
Attachments (0)
Change History (1)
comment:1 by , 15 years ago
Description: | modified (diff) |
---|---|
Milestone: | 0.11.6 |
Resolution: | → duplicate |
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
You didn't specify which Trac version you were using. I'd say 0.11, as r7286 should have fixed this issue.
Please upgrade to a later version (see TracDownload).
If you can reproduce this with a newer version, please reopen and show us the content of
result
(add some logging statements, e.g.self.log.critical('Before unicode error %r [%d]', result, col_idx)
).Likely a duplicate of #3908.