Closed Bug 691212 Opened 14 years ago Closed 14 years ago

Curly quotes, ellipsis and other jolly characters : not very pretty

Categories

(bugzilla.mozilla.org :: General, defect)

Production
x86_64
macOS
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 691211

People

(Reporter: nicolas.barbulesco, Unassigned)

Details

Camino version 2.0.9 (1.9.0.19 2011091218). Mac OS X 10.6.8. I go to https://bugzilla.mozilla.org and I submit a new bug. I enter this text : “Move the tab to a new window” : do not reload the page In the screen, my entered text appears fine. In a next screen, I get this Summary field, not very pretty : see screen photo http://screencast.com/t/R0F9mEnw66z . This is incorrect. I must get the exact string I had entered. Please fix that bug(s). In Camino or in Bugzilla ? Thanks. Nicolas
The curly quotes are represented in UTF-8 as three-byte sequences, but then each of the individual byte values has been treated as a separate character code in its own right. I think something - either at the browser or server end - is getting the text encoding wrong and treating a UTF-8 byte stream as if it were ISO Latin 1. Do you see the same problem if you use a different browser?
I am unable to reproduce this issue. Can you give more details what steps are you taking? Are you using the standard bug form (advanced) or are you using the guided bug form? The screen shot you provide is the view from the standard bug form which does not have a previous page. Where are you entering the summary and then showing your screenshot as the next page? Thanks dkl
Now, similar scenarios, similar problems : I enter this text : “Save as…” : ask where to save I get this Summary field, rather not pretty : screen photo http://screencast.com/t/UzxgAjG6k Here is my camino ;-) : http://screencast.com/t/lKz5pkqFdSh Nicolas
Summary: Curly quotes : not very pretty → Curly quotes, ellipsis and other jolly characters : not very pretty
Guessing this may be a bugzilla problem, where UTF-8 text is not tagged/served with the proper charset in certain situations. It looks like when the summary is copied from the "Bugzilla Helper" form to the standard Bug Entry form, characters that are outside the Latin-1 codepage (or perhaps characters with Unicode values > 255?) get converted to UTF-8 byte sequences, but then those individual bytes get treated as separate character codes when putting the text into the new form field. As characters outside the ASCII range (but still < 255) seem to be preserved without changing into UTF-8 sequences, I think some piece of code must be incorrectly deciding whether/where an encoding step is needed, resulting in a "mixed" string where some (non-ASCII) characters are still single (Latin-1) bytes, while others have been encoded as UTF-8. I was able to reproduce a scenario similar to http://screencast.com/t/lKz5pkqFdSh using a Firefox Nightly build on OS X, so it's not specific to Camino.
Status: UNCONFIRMED → NEW
Ever confirmed: true
This is a dupe of bug 691211; he filed them both at essentially the same time in two different products. There's no need for both bugs, especially if the reporter knows exactly where to file them. Nicholas, I've asked Gerv to suspend your Bugzilla account until you can demonstrate that you know how to use Bugzilla properly. Your recent behaviour is not conducive to anyone getting useful work done. Stop it.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Oops, meant to do that earlier when I commented.
Status: RESOLVED → VERIFIED
(In reply to Chris Lawson from comment #5) > This is a dupe of bug 691211; he filed them both at essentially the same > time in two different products. I wanted to report one bug for both products, thus allowing it to narrow the scope when known more precisely. But Bugzilla does not allow to choose more than one component for one request. Which is a really big lack, about which I had made a request for improvement. > There's no need for both bugs, especially if > the reporter knows exactly where to file them. I did not know where to report this bug. Camino or Bugzilla ? So I told both. These are the Web browser and the Web site / Web app : rather different things. Which are made by different people. > Nicholas, I've asked Gerv to suspend your Bugzilla account until you can > demonstrate that you know how to use Bugzilla properly. Because I take time to investigate and reproduce and record and report and explain bugs and improvement requests, in order to help fixing bugs and improving pieces of software for everyone. Very nice !
(In reply to Nicolas Barbulesco from comment #8) > (In reply to Chris Lawson from comment #5) > > > This is a dupe of bug 691211; he filed them both at essentially the same > > time in two different products. > > I wanted to report one bug for both products, thus allowing it to narrow the > scope when known more precisely. But Bugzilla does not allow to choose more > than one component for one request. Which is a really big lack, about which > I had made a request for improvement. No, that's by design; bugs are supposed to be for one specific code issue. In this case, the bug in question is clearly NOT a Camino issue. If you're ever unsure where to file a bug, just file it in the one place you think it fits best and trust that our triage teams will move it to the right place, if necessary. In the meantime, we'd appreciate not being treated like we don't know what we're doing.
You need to log in before you can comment on or make changes to this bug.