Closed
Bug 424962
Opened 17 years ago
Closed 16 years ago
Firefox 2 fails to render decomposed unicode umlauts correctly
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: macmaN, Unassigned)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12
Leopard 10.5.2, FF 2.0.0.12
Searching bugzilla for "unicode", "decomposed", "utf", "umlaut" did not produce information about this, so I am creating a new bug.
I am checking in subversion commits using svnX with log messages containing Estonian umlauts. svnX uses command line svn binaries in the background. I am viewing subversion information through everyone's favorite project environment trac, the problem shows up in Timeline and other pages where the log messages are displayed.
svn client uses decomposed unicode characters, I recompiled my svn binary according to this:
http://subversion.tigris.org/issues/show_bug.cgi?id=2464
There is additional information about Mac Firefox having problems with decomposed Unicode characters already from 2006:
http://earthlingsoft.net/ssp/blog/2006/07/unicode_normalisation
Safari 3 shows everything in question correctly. Curiously, Firefox 3 Beta 4 also shows everything in question correctly. Therefore it seems something in the Firefox font rendering engine has been altered to handle this. But since my whole browsing ecosystem only runs on FF2 for now, it'd be nice to get some information if it's possible to fix this.
Reproducible: Always
Steps to Reproduce:
View attached HTML page.
Actual Results:
Umlauts are displayed with an empty box instead of the accent.
Expected Results:
Normal umlaut display.
Reporter | ||
Comment 1•17 years ago
|
||
Reporter | ||
Comment 2•17 years ago
|
||
Reporter | ||
Updated•17 years ago
|
Version: unspecified → 2.0 Branch
Reporter | ||
Comment 3•16 years ago
|
||
i'm pretty sure it makes sense to close this as irrelevant by now.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•