Opened 20 years ago
Closed 19 years ago
#859 closed defect (duplicate)
trac-admin does not convert national characters to utf-8 and back
Reported by: | anonymous | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | admin/console | Version: | devel |
Severity: | major | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
all characters entered from keyboard (for example 'component add "national-characters-here") go to the database without converting to utf-8.
so in web interface they are shown incorrectly.
Attachments (0)
Change History (15)
comment:1 by , 20 years ago
Priority: | normal → highest |
---|
comment:3 by , 20 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:4 by , 20 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Don't close as anonymous or without a comment.
comment:5 by , 20 years ago
With Red Hat 9 and Fedora Core ½/3 all entered text is in utf-8 unless you change the default setup. Shouldn't this be checked before converting from and to utf-8? With FC3 I have only a small problem with trac-admin while erasing multibyte characters with backspace, but this is going to be fixed soon I hope :)
comment:6 by , 20 years ago
Owner: | changed from | to
---|---|
Status: | reopened → new |
comment:7 by , 20 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:8 by , 20 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Please don't close without a comment.
comment:9 by , 20 years ago
well all that sounds very good i love this applicatoin - it is great thx
comment:11 by , 20 years ago
Component: | trac-admin → general |
---|---|
Keywords: | aaaa added |
Priority: | highest → normal |
Severity: | critical → major |
Version: | devel → 0.6.1 |
testuojam
comment:12 by , 20 years ago
Component: | general → trac-admin |
---|---|
Keywords: | aaaa removed |
Version: | 0.6.1 → devel |
Please don't abuse the system
comment:13 by , 19 years ago
Owner: | removed |
---|---|
Status: | reopened → new |
comment:14 by , 19 years ago
Owner: | set to |
---|
This incident is probably tied to #2394.
(sorry for the new status instead of reopened, clearing out the owner seems to reset the status)
comment:15 by , 19 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |