The tweet referred to in the URL has a bunch of diacritics that aren't being combined. This is the case in Chrome, Safari, *and* Firefox. http://grab.by/a9sj is how Twitter for Mac renders this text. Is Twitter rendering this wrong, or are we?
Well, I suppose Twitter's rendering is in some sense closer to being "right". But the main issue here is that many of the characters are not supported by the primary fonts in the CSS font-family property, and so fallback happens - and we probably end up getting characters from several different fallback fonts. And proper diacritic positioning - which we *do* support via harfbuzz and OpenType fonts with 'mark' and 'mkmk' features - will not happen across font changes, as that completely breaks all shaping. The main thing that would help this (aside from disabling the page's CSS and setting your browser's font to something like Code2000 that probably supports all the characters involved) would be to ensure that we do font selection on a character cluster basis, instead of treating each individual Unicode character separately. That's bug 543200. (Note that the result would still be dependent on the quality of diacritic support in the font that we end up using, but searching for a font that supports the entire base+diacritics cluster would greatly improve the odds.)
Depends on: 543200
You need to log in before you can comment on or make changes to this bug.