Closed Bug 276964 Opened 20 years ago Closed 19 years ago

Problem with tables and french caracters

Categories

(Core :: Internationalization, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: mail, Assigned: smontagu)

References

()

Details

(Keywords: qawanted)

Hello,

Here is my site : http://www.yov408.com/html/ideabox.php.
On my computer with Windows XP and firefox 1.0 English version with no
extensions/add-ons and skins: I have a problem with the height of the lines of
the tables. For example on the above page, if you reload the page several times
you will see that randomly the big table with the 'ideas' sometimes appears with
a doubled heighted lines. This happens about once every ten reloads. There is
also the same problem with french characters, every tenth reloads, they don't
appear and there is a ? instead of them. I insist on the fact that theese two
bugs are random and appear on only about one load out of ten.
Thanks for this great browser.
Hope this will help !

Regards,

Fred
The markup says:
<META NAME="Content-Type" CONTENT="text/html; charset=ISO-2022-JP">

The server says:
 6 Content-Type: text/html

When problem occurs "View - Character Encoding" show "Western (ISO-8859-1)",
but if I then visit some other page and go back, the same menu item now says
"Japanese (ISO-2022-JP)" and the font is now different also.
Assignee: firefox → dbaron
Component: General → Style System (CSS)
OS: Windows XP → All
Product: Firefox → Core
QA Contact: firefox.general → ian
Version: 1.0 Branch → Trunk
Assignee: dbaron → smontagu
Component: Style System (CSS) → Internationalization
Keywords: qawanted
QA Contact: ian → amyy
> <META NAME="Content-Type" CONTENT="text/html; charset=ISO-2022-JP">

The above should read
 
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-2022-JP">

I'm wondering how 'ISO-2022-JP' is picked up sometimes although I can't
reproduce it. 
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.