| 2008-05-10 13:53:59 |
André Pirard |
bug |
|
|
added bug |
| 2008-05-10 13:53:59 |
André Pirard |
bug |
|
|
added attachment 'Screenshot-Le Tr�sor de la Langue Fran�aise Informatis� - Mozilla Firefox 3 Beta 3.png' (Screenshot-Le Tr�sor de la Langue Fran�aise Informatis� - Mozilla Firefox 3 Beta 3.png) |
| 2008-05-10 13:58:35 |
André Pirard |
firefox: status |
New |
Confirmed |
|
| 2008-05-10 19:01:50 |
John Vivirito |
firefox: status |
Confirmed |
Incomplete |
|
| 2008-05-10 19:03:37 |
John Vivirito |
firefox: status |
Incomplete |
Confirmed |
|
| 2008-05-10 19:03:58 |
John Vivirito |
bug |
|
|
assigned to firefox-3.0 (Ubuntu) |
| 2008-05-10 19:04:11 |
John Vivirito |
firefox-3.0: status |
New |
Confirmed |
|
| 2008-05-11 14:15:13 |
André Pirard |
bug |
|
|
added attachment 'UTF-8 atilf Mozilla Firefox 3 Beta 5.png' (UTF-8 atilf Mozilla Firefox 3 Beta 5.png) |
| 2008-05-11 21:29:08 |
Alexander Sack |
firefox-3.0: status |
Confirmed |
Invalid |
|
| 2008-05-11 21:29:16 |
Alexander Sack |
firefox: status |
Confirmed |
Invalid |
|
| 2008-05-12 15:33:23 |
Alexander Sack |
firefox-3.0: status |
Invalid |
Incomplete |
|
| 2008-05-12 15:33:23 |
Alexander Sack |
firefox: status |
Invalid |
Won't Fix |
|
| 2008-09-06 12:24:23 |
André Pirard |
bug |
|
|
added attachment 'I_do_want_my_prize.png' (I_do_want_my_prize.png) |
| 2008-11-10 23:29:02 |
Mante |
bug |
|
|
added attachment 'google.it.text.input.length.jpg' (google.it.text.input.length.jpg) |
| 2008-11-24 17:44:57 |
André Pirard |
bug |
|
|
added attachment 'Screenshot-Mozilla Firefox.png' (Screenshot-Mozilla Firefox.png) |
| 2009-06-15 06:42:10 |
André Pirard |
attachment added |
|
Screenshot-Recherche d'un mot - Mozilla Firefox.png http://launchpadlibrarian.net/27912887/Screenshot-Recherche%20d%27un%20mot%20-%20Mozilla%20Firefox.png |
|
| 2010-08-22 14:08:53 |
papukaija |
bug |
|
|
added subscriber papukaija |
| 2010-09-16 00:27:30 |
André Pirard |
attachment added |
|
Screenshot-Mozilla Firefox.png https://bugs.launchpad.net/bugs/228988/+attachment/1591307/+files/Screenshot-Mozilla%20Firefox.png |
|
| 2010-09-16 00:27:30 |
André Pirard |
attachment added |
|
Screenshot-2.png https://bugs.launchpad.net/bugs/228988/+attachment/1591308/+files/Screenshot-2.png |
|
| 2010-09-16 00:30:45 |
André Pirard |
attachment added |
|
Screenshot-Mozilla Firefox.png https://bugs.launchpad.net/bugs/228988/+attachment/1591313/+files/Screenshot-Mozilla%20Firefox.png |
|
| 2010-09-16 00:30:45 |
André Pirard |
attachment added |
|
Screenshot-2.png https://bugs.launchpad.net/bugs/228988/+attachment/1591314/+files/Screenshot-2.png |
|
| 2010-09-16 11:24:55 |
papukaija |
tags |
|
hardy jaunty |
|
| 2010-09-16 16:27:45 |
papukaija |
tags |
hardy jaunty |
hardy jaunty lucid |
|
| 2010-09-16 16:43:16 |
papukaija |
attachment added |
|
tlf_utf8.html https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/228988/+attachment/1594356/+files/tlf_utf8.html |
|
| 2010-09-19 13:54:25 |
André Pirard |
attachment added |
|
Windows_XP-Firefox_3.6.10.png https://bugs.launchpad.net/bugs/228988/+attachment/1608457/+files/Windows_XP-Firefox_3.6.10.png |
|
| 2010-09-19 13:54:25 |
André Pirard |
attachment added |
|
Windows_XP-Internet_Explorer_6.0.2900.5512.xpsp.080413-2111.png https://bugs.launchpad.net/bugs/228988/+attachment/1608458/+files/Windows_XP-Internet_Explorer_6.0.2900.5512.xpsp.080413-2111.png |
|
| 2010-10-01 02:42:25 |
André Pirard |
attachment added |
|
ORWerr.png https://bugs.launchpad.net/bugs/228988/+attachment/1660869/+files/ORWerr.png |
|
| 2010-10-01 02:42:25 |
André Pirard |
attachment added |
|
ORWerr2.png https://bugs.launchpad.net/bugs/228988/+attachment/1660870/+files/ORWerr2.png |
|
| 2010-10-01 02:42:25 |
André Pirard |
attachment added |
|
ORWerr.html https://bugs.launchpad.net/bugs/228988/+attachment/1660871/+files/ORWerr.html |
|
| 2010-10-30 13:20:47 |
papukaija |
bug task added |
|
firefox |
|
| 2010-10-30 13:20:59 |
papukaija |
firefox: status |
New |
Incomplete |
|
| 2010-10-31 11:38:27 |
papukaija |
affects |
firefox (Ubuntu) |
ubuntu |
|
| 2010-10-31 11:39:57 |
papukaija |
affects |
firefox-3.0 (Ubuntu) |
firefox (Ubuntu) |
|
| 2010-10-31 11:58:39 |
papukaija |
bug watch added |
|
https://bugzilla.mozilla.org/show_bug.cgi?id=253575 |
|
| 2010-10-31 11:58:39 |
papukaija |
bug watch added |
|
https://bugzilla.mozilla.org/show_bug.cgi?id=254868 |
|
| 2010-10-31 13:12:14 |
André Pirard |
summary |
Firefox can display a page with the wrong encoding |
Firefox can display a page with the wrong default encoding |
|
| 2010-10-31 13:53:45 |
André Pirard |
description |
Since I'm using it, I see Firefox (2.X and 3.0bX) sometimes display pages using the wrong character encoding. Sometime a page will display correctly, later the same page won't, without any apparent reason why there's a difference.
I have first introduced Bug #206884 but, although it says exactly this, it turns out that several people misunderstood it, that it became a mess and that adding more explanation to it would make the mess even worse.
So I'm trying to make it clear and orderly in here, please read more detail in #206884.
And, obviously, make #206884 a duplicate of this one, not the opposite.
I made tests with http://atilf.atilf.fr/tlf.htm which often displays to me as shown in the attachment.
I even found a way to produce a problem.
This was Problem #1 and here is the procedure to produce it.
1) clear the said URL from history [any occurrence of the hostname in address bar dropdown]
2) open a new window or tag and do the following in it
3) set View|Character Encoding to UTF-8 (or anything but ISO889-1)
4) type that URL in the address bar and display page
5) the page displays using the wrong encoding (as the attachment, using UTF-8)
Repeat 1-5, setting ISO889-1 instead, and you get a correct display.
See an alternate procedure and more comments at the end of this text.
The obvious problem is that something done before the page displays produces an incorrect character set usage. In this case, we did it willingly but it may be the same problem that occurs unwillingly.
Obviously, all pages should contain all the information necessary to display correctly and ONLY AFTER a page was displayed should the user be able to try to display it using other encodings.
The header of that page is :
<HEAD>
<TITLE>
Le Trésor de la Langue Française Informatisé
</TITLE>
<link rel="stylesheet" type="text/css" href="atilf.css">
</HEAD>
We notice that this header doesn't specify the encoding.
As far as I know, the default encoding is ISO8858-1.
Hence, displaying the page in UTF-8 is always incorrect, unless the user changes the encoding after it was displayed.
Additional problem #2
I'll sketch it here. Please also read the bulk in #206884.
I was trying to find what could make determining the page encoding uncertain and I found this.
1) Content OptionsPreferences|Fonts & Colors|Character Encoding
The character encoding selected here will be used to display pages that do not specify which encoding to use.
This preference is unneeded, as, in my mind, the default is always ISO8859-1.
Allowing the user to change the default sure is a way to run into problems.
The Web will show you people telling others to set it back to ISO8859-1.
Yet ...
2) I tried to set this default setting to UTF-8 and, to my amazement, the test URL displayed correctly.
3) It may be that Firefox remembers the pages encodings in history (why I'm asking to clear it).
If that's a good feature once the user manually corrects the encoding for a page, it's less appropriate when a user who doesn't know how to change this encoding is hit by this occasional problem as the page encoding will be wrong for history's life instead of occasionally.
4) My discussion about how the standards badly define the encoding and the default encoding is for the Firefox developpers to notify those who write the standards.
PS:
Having spent hours trying to explain this simple problem and making tests, I just found another way to demonstrate it :
0) Use a freshly started, otherwise empty, Firefox
1) Again, clear the said URL from history [any occurrence of the hostname in address bar dropdown] as if it were the first time you use that URL
2) Use Google to search "Trésor Langue Française Informatisé", check that you get our URL
3) Right-click on link to "Open ... in new Tab"
4) the page displays using the wrong encoding (as the attachment, using UTF-8)
This is more like a user would do.
I thought that the UTF-8 setting in a freshly opened page or tab was because Google uses UTF-8, but I finally see that any empty tab ow window I open has UTF-8 set.
But, again, the problem is not what is set but that Firefox uses it as default instead of ISO8859-1.
Any page should display correctly whatever is done before it starts displaying. |
Since I'm using it, I see Firefox (2.X and 3.X) sometimes display pages using the wrong character encoding. Sometime a page will display correctly, later the same page won't, without any apparent reason why there's a difference.
Update:
------
Truly, there's something unpredictable in this behaviour of Firefox and of the presented test cases.
Hence, I hereby mention a procedure that's reproducible on all my freshly installed systems but unfortunately not on all other ones (mainly US ones)
display http://atilf.atilf.fr
Click 'Entrez dans le TLF'
Fill in search field: 'erreur', click 'Valider 1'
Select the word 'ERREUR', a window pops up
Click on 'le TLF1' in that window
The pop up window invariably displays ISO8859-1 as UTF-8 as shown in
http://launchpadlibrarian.net/55706907/Screenshot-Mozilla%20Firefox.png
-----
I have first introduced Bug #206884 but, although it says exactly this, it turns out that several people misunderstood it, that it became a mess and that adding more explanation to it would make the mess even worse.
So I'm trying to make it clear and orderly in here, please read more detail in #206884.
And, obviously, make #206884 a duplicate of this one, not the opposite.
I made tests with http://atilf.atilf.fr/tlf.htm which often displays to me as shown in the attachment.
I even found a way to produce a problem.
This was Problem #1 and here is the procedure to produce it.
1) clear the said URL from history [any occurrence of the hostname in address bar dropdown]
2) open a new window or tag and do the following in it
3) set View|Character Encoding to UTF-8 (or anything but ISO889-1)
4) type that URL in the address bar and display page
5) the page displays using the wrong encoding (as the attachment, using UTF-8)
Repeat 1-5, setting ISO889-1 instead, and you get a correct display.
See an alternate procedure and more comments at the end of this text.
The obvious problem is that something done before the page displays produces an incorrect character set usage. In this case, we did it willingly but it may be the same problem that occurs unwillingly.
Obviously, all pages should contain all the information necessary to display correctly and ONLY AFTER a page was displayed should the user be able to try to display it using other encodings.
The header of that page is :
<HEAD>
<TITLE>
Le Trésor de la Langue Française Informatisé
</TITLE>
<link rel="stylesheet" type="text/css" href="atilf.css">
</HEAD>
We notice that this header doesn't specify the encoding.
As far as I know, the default encoding is ISO8858-1.
Hence, displaying the page in UTF-8 is always incorrect, unless the user changes the encoding after it was displayed.
Additional problem #2
I'll sketch it here. Please also read the bulk in #206884.
I was trying to find what could make determining the page encoding uncertain and I found this.
1) Content OptionsPreferences|Fonts & Colors|Character Encoding
The character encoding selected here will be used to display pages that do not specify which encoding to use.
This preference is unneeded, as, in my mind, the default is always ISO8859-1.
Allowing the user to change the default sure is a way to run into problems.
The Web will show you people telling others to set it back to ISO8859-1.
Yet ...
2) I tried to set this default setting to UTF-8 and, to my amazement, the test URL displayed correctly.
3) It may be that Firefox remembers the pages encodings in history (why I'm asking to clear it).
If that's a good feature once the user manually corrects the encoding for a page, it's less appropriate when a user who doesn't know how to change this encoding is hit by this occasional problem as the page encoding will be wrong for history's life instead of occasionally.
4) My discussion about how the standards badly define the encoding and the default encoding is for the Firefox developpers to notify those who write the standards.
PS:
Having spent hours trying to explain this simple problem and making tests, I just found another way to demonstrate it :
0) Use a freshly started, otherwise empty, Firefox
1) Again, clear the said URL from history [any occurrence of the hostname in address bar dropdown] as if it were the first time you use that URL
2) Use Google to search "Trésor Langue Française Informatisé", check that you get our URL
3) Right-click on link to "Open ... in new Tab"
4) the page displays using the wrong encoding (as the attachment, using UTF-8)
This is more like a user would do.
I thought that the UTF-8 setting in a freshly opened page or tab was because Google uses UTF-8, but I finally see that any empty tab ow window I open has UTF-8 set.
But, again, the problem is not what is set but that Firefox uses it as default instead of ISO8859-1.
Any page should display correctly whatever is done before it starts displaying.
|
|
| 2010-10-31 13:54:19 |
André Pirard |
description |
Since I'm using it, I see Firefox (2.X and 3.X) sometimes display pages using the wrong character encoding. Sometime a page will display correctly, later the same page won't, without any apparent reason why there's a difference.
Update:
------
Truly, there's something unpredictable in this behaviour of Firefox and of the presented test cases.
Hence, I hereby mention a procedure that's reproducible on all my freshly installed systems but unfortunately not on all other ones (mainly US ones)
display http://atilf.atilf.fr
Click 'Entrez dans le TLF'
Fill in search field: 'erreur', click 'Valider 1'
Select the word 'ERREUR', a window pops up
Click on 'le TLF1' in that window
The pop up window invariably displays ISO8859-1 as UTF-8 as shown in
http://launchpadlibrarian.net/55706907/Screenshot-Mozilla%20Firefox.png
-----
I have first introduced Bug #206884 but, although it says exactly this, it turns out that several people misunderstood it, that it became a mess and that adding more explanation to it would make the mess even worse.
So I'm trying to make it clear and orderly in here, please read more detail in #206884.
And, obviously, make #206884 a duplicate of this one, not the opposite.
I made tests with http://atilf.atilf.fr/tlf.htm which often displays to me as shown in the attachment.
I even found a way to produce a problem.
This was Problem #1 and here is the procedure to produce it.
1) clear the said URL from history [any occurrence of the hostname in address bar dropdown]
2) open a new window or tag and do the following in it
3) set View|Character Encoding to UTF-8 (or anything but ISO889-1)
4) type that URL in the address bar and display page
5) the page displays using the wrong encoding (as the attachment, using UTF-8)
Repeat 1-5, setting ISO889-1 instead, and you get a correct display.
See an alternate procedure and more comments at the end of this text.
The obvious problem is that something done before the page displays produces an incorrect character set usage. In this case, we did it willingly but it may be the same problem that occurs unwillingly.
Obviously, all pages should contain all the information necessary to display correctly and ONLY AFTER a page was displayed should the user be able to try to display it using other encodings.
The header of that page is :
<HEAD>
<TITLE>
Le Trésor de la Langue Française Informatisé
</TITLE>
<link rel="stylesheet" type="text/css" href="atilf.css">
</HEAD>
We notice that this header doesn't specify the encoding.
As far as I know, the default encoding is ISO8858-1.
Hence, displaying the page in UTF-8 is always incorrect, unless the user changes the encoding after it was displayed.
Additional problem #2
I'll sketch it here. Please also read the bulk in #206884.
I was trying to find what could make determining the page encoding uncertain and I found this.
1) Content OptionsPreferences|Fonts & Colors|Character Encoding
The character encoding selected here will be used to display pages that do not specify which encoding to use.
This preference is unneeded, as, in my mind, the default is always ISO8859-1.
Allowing the user to change the default sure is a way to run into problems.
The Web will show you people telling others to set it back to ISO8859-1.
Yet ...
2) I tried to set this default setting to UTF-8 and, to my amazement, the test URL displayed correctly.
3) It may be that Firefox remembers the pages encodings in history (why I'm asking to clear it).
If that's a good feature once the user manually corrects the encoding for a page, it's less appropriate when a user who doesn't know how to change this encoding is hit by this occasional problem as the page encoding will be wrong for history's life instead of occasionally.
4) My discussion about how the standards badly define the encoding and the default encoding is for the Firefox developpers to notify those who write the standards.
PS:
Having spent hours trying to explain this simple problem and making tests, I just found another way to demonstrate it :
0) Use a freshly started, otherwise empty, Firefox
1) Again, clear the said URL from history [any occurrence of the hostname in address bar dropdown] as if it were the first time you use that URL
2) Use Google to search "Trésor Langue Française Informatisé", check that you get our URL
3) Right-click on link to "Open ... in new Tab"
4) the page displays using the wrong encoding (as the attachment, using UTF-8)
This is more like a user would do.
I thought that the UTF-8 setting in a freshly opened page or tab was because Google uses UTF-8, but I finally see that any empty tab ow window I open has UTF-8 set.
But, again, the problem is not what is set but that Firefox uses it as default instead of ISO8859-1.
Any page should display correctly whatever is done before it starts displaying.
|
Since I'm using it, I see Firefox (2.X and 3.X) sometimes display pages using the wrong character encoding. Sometime a page will display correctly, later the same page won't, without any apparent reason why there's a difference.
Update:
------
Truly, there's something unpredictable in this behaviour of Firefox and of the presented test cases. Hence, I hereby mention a procedure that's reproducible on all my freshly installed systems but unfortunately not on all other ones (mainly US ones)
display http://atilf.atilf.fr
Click 'Entrez dans le TLF'
Fill in search field: 'erreur', click 'Valider 1'
Select the word 'ERREUR', a window pops up
Click on 'le TLF1' in that window
The pop up window invariably displays ISO8859-1 as UTF-8 as shown in
http://launchpadlibrarian.net/55706907/Screenshot-Mozilla%20Firefox.png
-----
I have first introduced Bug #206884 but, although it says exactly this, it turns out that several people misunderstood it, that it became a mess and that adding more explanation to it would make the mess even worse.
So I'm trying to make it clear and orderly in here, please read more detail in #206884.
And, obviously, make #206884 a duplicate of this one, not the opposite.
I made tests with http://atilf.atilf.fr/tlf.htm which often displays to me as shown in the attachment.
I even found a way to produce a problem.
This was Problem #1 and here is the procedure to produce it.
1) clear the said URL from history [any occurrence of the hostname in address bar dropdown]
2) open a new window or tag and do the following in it
3) set View|Character Encoding to UTF-8 (or anything but ISO889-1)
4) type that URL in the address bar and display page
5) the page displays using the wrong encoding (as the attachment, using UTF-8)
Repeat 1-5, setting ISO889-1 instead, and you get a correct display.
See an alternate procedure and more comments at the end of this text.
The obvious problem is that something done before the page displays produces an incorrect character set usage. In this case, we did it willingly but it may be the same problem that occurs unwillingly.
Obviously, all pages should contain all the information necessary to display correctly and ONLY AFTER a page was displayed should the user be able to try to display it using other encodings.
The header of that page is :
<HEAD>
<TITLE>
Le Trésor de la Langue Française Informatisé
</TITLE>
<link rel="stylesheet" type="text/css" href="atilf.css">
</HEAD>
We notice that this header doesn't specify the encoding.
As far as I know, the default encoding is ISO8858-1.
Hence, displaying the page in UTF-8 is always incorrect, unless the user changes the encoding after it was displayed.
Additional problem #2
I'll sketch it here. Please also read the bulk in #206884.
I was trying to find what could make determining the page encoding uncertain and I found this.
1) Content OptionsPreferences|Fonts & Colors|Character Encoding
The character encoding selected here will be used to display pages that do not specify which encoding to use.
This preference is unneeded, as, in my mind, the default is always ISO8859-1.
Allowing the user to change the default sure is a way to run into problems.
The Web will show you people telling others to set it back to ISO8859-1.
Yet ...
2) I tried to set this default setting to UTF-8 and, to my amazement, the test URL displayed correctly.
3) It may be that Firefox remembers the pages encodings in history (why I'm asking to clear it).
If that's a good feature once the user manually corrects the encoding for a page, it's less appropriate when a user who doesn't know how to change this encoding is hit by this occasional problem as the page encoding will be wrong for history's life instead of occasionally.
4) My discussion about how the standards badly define the encoding and the default encoding is for the Firefox developpers to notify those who write the standards.
PS:
Having spent hours trying to explain this simple problem and making tests, I just found another way to demonstrate it :
0) Use a freshly started, otherwise empty, Firefox
1) Again, clear the said URL from history [any occurrence of the hostname in address bar dropdown] as if it were the first time you use that URL
2) Use Google to search "Trésor Langue Française Informatisé", check that you get our URL
3) Right-click on link to "Open ... in new Tab"
4) the page displays using the wrong encoding (as the attachment, using UTF-8)
This is more like a user would do.
I thought that the UTF-8 setting in a freshly opened page or tab was because Google uses UTF-8, but I finally see that any empty tab ow window I open has UTF-8 set.
But, again, the problem is not what is set but that Firefox uses it as default instead of ISO8859-1.
Any page should display correctly whatever is done before it starts displaying.
|
|
| 2010-10-31 22:48:28 |
André Pirard |
bug watch added |
|
https://bugzilla.mozilla.org/show_bug.cgi?id=608609 |
|
| 2010-11-01 13:44:23 |
papukaija |
firefox: status |
Incomplete |
New |
|
| 2010-11-01 13:45:40 |
papukaija |
firefox: importance |
Undecided |
Unknown |
|
| 2010-11-01 13:45:40 |
papukaija |
firefox: status |
New |
Unknown |
|
| 2010-11-01 13:45:40 |
papukaija |
firefox: remote watch |
|
Mozilla Bugzilla #608609 |
|
| 2010-11-01 13:46:16 |
papukaija |
firefox (Ubuntu): status |
Incomplete |
New |
|
| 2010-11-28 04:45:54 |
Bug Watch Updater |
firefox: status |
Unknown |
New |
|
| 2010-11-28 04:45:54 |
Bug Watch Updater |
firefox: importance |
Unknown |
Medium |
|
| 2012-08-05 16:12:52 |
Launchpad Janitor |
firefox (Ubuntu): status |
New |
Confirmed |
|
| 2017-06-14 08:10:35 |
Henri Sivonen |
bug watch added |
|
https://bugzilla.mozilla.org/show_bug.cgi?id=844115 |
|
| 2017-06-14 08:42:48 |
Bug Watch Updater |
firefox: status |
New |
Invalid |
|
