Closed
Bug 44343
Opened 25 years ago
Closed 20 years ago
Bugzilla doesn't handle unicode characters in forms
Categories
(Bugzilla :: Bugzilla-General, defect, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 126266
People
(Reporter: pete_a90, Assigned: justdave)
Details
When I entered unicode characters in this description field when submitting a bug, all the characters that were unicode displayed as %uHHHH where H is a hex value. You should replace the %u with #&x and add a ; at the end so %uHHHH becomes &#xHHHH; when outputting to html.
Updated•24 years ago
|
Whiteboard: 2.14
Updated•24 years ago
|
Whiteboard: 2.14 → 2.16
Assignee | ||
Comment 1•24 years ago
|
||
moving to real milestones...
Target Milestone: --- → Bugzilla 2.16
Updated•24 years ago
|
Priority: P3 → P2
Comment 2•23 years ago
|
||
I have this problem (0.9.3): <textarea> ē e&772; -- e with combining macron </textarea> The macronised e (e?) is shown in the textarea rather than the entity (e&#772;), but when the form is submitted, neither the macronised e or the e with entity is sent, rather I get the string "e?". The best behaviour would be (as MISE 5 does) to send the macronised e. The second best would be to send the uninterpreted entity, so that at least the information is not lost.
Comment 3•23 years ago
|
||
moving. I know that collabnet would like to see this happen.
Assignee: tara → justdave
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: other → 2.10
Assignee | ||
Comment 4•23 years ago
|
||
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
What is the status on this bug? We need to use bugzilla in a multi-language environment, where japanese characters may need to be entered into comments, etc.
Comment 6•22 years ago
|
||
It works fine, as long as you've set the charset for each of the pages to UTF-8. We're storing Chinese, Japanese, Korean, and Arabic in our Bugzilla installation, using 2.16.1 (though we started doing this in 2.14). With templatization it becomes easy: just create a local version of header.html.tmpl. I don't think I made any other changes. This is related to bug 126266.
Comment 7•21 years ago
|
||
Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being retargeted to 2.20 If you plan to act on one immediately, go ahead and pull it back to 2.18.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Assignee | ||
Comment 8•20 years ago
|
||
bug 126266 is basically about this, and will solve this when it lands. *** This bug has been marked as a duplicate of 126266 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Whiteboard: 2.16
Target Milestone: Bugzilla 2.20 → ---
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•