Open Bug 620364 Opened 12 years ago Updated 3 years ago

Error UTF-8 encoded

Categories

(Core :: General, defect)

defect
Not set
normal

Tracking

()

UNCONFIRMED

People

(Reporter: mail, Unassigned)

References

()

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:2.0b9pre) Gecko/20101219 Firefox/4.0b9pre
Build Identifier: 

Does not display UTF-8 on the link, you can see an example of the text.
Affects the display of the operating system and browser.

Reproducible: Always
This is wfm using  Mozilla/5.0 (Windows NT 6.1; rv:2.0b9pre) Gecko/20101217 Firefox/4.0b9pre SeaMonkey/2.1b2pre

>Affects the display of the operating system and browser.
Affects the display of the operating system ?
What do you mean with that ?
Worksforme as well.  View menu says it's UTF-8, and all the non-ASCII bits show up fine.  Reporter, can you please attach a screenshot of what you see?
works for me - Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b9pre) Gecko/20110103 Firefox/4.0b9pre

Server is sending the correct mime type. Possibly the user does not have international/symbol fonts installed that are needed for the page?
Attached image Screen
An article on this issue: http://habrahabr.ru/blogs/browsers/110331/
For me personally, in different browsers totally different. Well, firefox as you can see the screenshot incorrectly displays.
Problems with language in a larger case no. Problems with:
Mathematics and stsientses
Nicer typography in plain text Phils
Combining charatsters
Thai (UCS Level 2)
Box drawing alignment
Something like this should happen: http://img522.imageshack.us/img522/7060/1292858076615.пнж
According to people in the article, these problems are mainly in Windows, support for displaying Unicode-characters is not complete.
I don't read Russian but the roughly translated article via Google translate seems to have some errors. 

It seems to suggest that Firefox does not use curly apostrophes which is false. If you search the document for flat quotes the first such instance is "A Christmas Carol" and if you search for the curly quotes the characters are correctly matched.

Alignment issues are going to be limitations of the monospace fonts on the OS. If a character is not found in a monospace font and is found in a proportional font browsers will use the proportional font thus breaking the alignment.

All the issues in the page I see look to be from monospaced fonts for my OS (Win7) failing to have the glyphs required by the document.
(In reply to Kevin Brosnan from comment #8)
> All the issues in the page I see look to be from monospaced fonts for my OS
> (Win7) failing to have the glyphs required by the document.

So not a firefox bug?

Status of https://bugs.launchpad.net/firefox/+bug/51554 is invalid, with the comment "I can't reproduce this in Ubuntu 12.10. I'm inclined to think this was actually a bug in the font (DejaVu Sans Mono) and not in Firefox itself"
Flags: needinfo?(kbrosnan)
On Windows 7 today's Firefox nightly. This install of Windows7 does not have any additional fonts installed. As I recall my comment 3 I had a system with the STIX fonts installed.

Firefox will use a proportional glyph if a monosapced glyph does not exist on the system. This will cause the text document to have an odd alignment on rows where Unicode monospaced glyphs do not exist on the system. 

I verified this assumption by opening the text document in Sublime text editor. It shows many instances where Windows does not have the correct monospaced glyph, it displays the Unicode missing glyph symbol rather than doing fallback.

I believe that doing fallback is the better thing to do for web browsers. Jonathan Kew would know for sure, or possibly there are older bugs to reference? If people want monospaced line drawing to work they should have a robust monospace font installed such as the ones provided by the STIX project. 

http://sourceforge.net/projects/stixfonts/files/latest/download
https://en.wikipedia.org/wiki/STIX_Fonts_project
http://www.stixfonts.org/
Flags: needinfo?(kbrosnan)

FYI, this reporter is gone - not responded to any bug reports. Perhaps this can be closed?

You need to log in before you can comment on or make changes to this bug.