More Firefox font rendering bugs

[ewx]

http://www.greenend.org.uk/rjk/junk/cc.html in Linux Firefox:

Windows Firefox is not really any better:

IE7 gets it right:

Konqueror doesn't even try:

I don't have Safari to hand right now.

I guess for best results send precomposed characters to the browser, and put up with bad rendering where none are available l-(

(These are the Firefox and Konqueror from Debian etch.)

Comments

[aardvark179.livejournal.com]

Searching and sorting is a different but related problem, you should find the results even if the user doesn't type the accents, and they should normally be ignored for sorting purposes as well.

[ewx.livejournal.com]

DisOrder has two contexts in which it orders unicode strings; firstly for display purposes, in which case, as you say, the same kind of normalization as done for search is probably the most appropriate; but it also uses track names as database keys, with an ordering that accounts for their filename structure. In that case they are normalized to NFC and accents and letter case are strictly preserved.

As it happens the use of NFC there, and also the conversion of all user commands to NFC, propagate through to the display of bits of track names, meaning that user interfaces will indeed get precomposed characters where available, minimizing the effect of the browser bug I started with l-)

[pm215]

How does it cope with Japanese track names, by the way?

[ewx.livejournal.com]

I've not tried any, I'm afraid...

[pm215]

I can provide you with some examples if you like :-)

[ewx.livejournal.com]

All I really need is artist/album/title, and some hints as to user expectation of processing of these names, rather than actual content. Then I can stuff them into my test scripts...