************************************************************* Considering that the more I write about this problem the less it's understood, I have introduced a new Bug #228988 where everything has been rewritten from scratch. PLEASE READ IT CAREFULLY, it's the last time I write, I have lost enough time. I set it to "confirmed", please correct statuses of both as needed ---->>> For obvious reasons, make this bug a duplicate of Bug #228988 rather than the opposite. *************************************************************
On 05/09/2008 07:58 PM, John Vivirito wrote : > Please read the following link about bug states before marking as confirmed. > https://wiki.ubuntu.com/MozillaTeam/Bugs/States?highlight=(mozilla) > marking as incomplete > I know why I do that. Some bugs I introduced would have been erased by a timeout threat because nobody came to set "confirmed" well after I provided the information they asked. You probably noticed that I'm willing to cooperate but I hate losing my time. Could you explain why this bug was reset to incomplete and then to complete again without any additional data being added? On 05/10/2008 02:38 AM, Alexander Sack wrote : > i can confirm that the semantic of the character encoding menu could be > improved. > I didn't really speak of a menu (which?) and its semantic of a character encoding. Did anyone try the procedure I wrote twice? I suppose that trying is why I was asked to write it a second time. What are your conclusions? Firefox should display the page using the wrong encoding. > However, unless someone comes up with a good idea, i doubt that this > will be fixable for 3.0. > I have the feeling that the fix is amazingly simple for both 2 and 3. > ** Summary changed: > > - Firefox uses the wrong display encoding > + fuzzy/confusing firefox View -> Character encoding menu semantics > The previous title was the correct one. The practical, most important problem is #1. The new title reflects Problem #2, the theory of specifying which encoding a page uses, especially default encoding. > ** Changed in: firefox (Ubuntu) > Importance: Undecided => Low > Status: Incomplete => Confirmed > If the bug occurs as often as I have seen it occur, it is of very high importance. (especially if easy to fix) It's been pesting me for months before I made this analysis. Of course, it occurs only to those needing the accented characters of ISO88859-1. (If you search the Web for discussions of this, please search in French). Thanks for your attention and for your Open devotion. -- fuzzy/confusing firefox View -> Character encoding menu semantics https://bugs.launchpad.net/bugs/206884 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
