On Mon, 2007-08-27 at 09:15 +0000, Rich Felker wrote: > After upgrading my system, the latest Pango renders U+200B (zero-width > space) visibly under certain conditions, as a "missing glyph" box > containing the hex value. Particularly, Pango seems to be a looking > for a glyph for this character matching the current language/script. > In my case, Tibetan characters adjacent to U+200B cause the > misrendering to happen. > > I first observed the problem on a Google search (in Iceweasel) but > have since been able to reproduce it in GTK+ text widgets by first > typing U+200B (using an input method) then moving the cursor before > the U+200B character and typing any Tibetan character. Thus, I am > fairly confident that the bug is in Pango itself and not GTK+ or > Iceweasel. > > I suspect the Tibetan fonts I am using lack a glyph for U+200B, but > Pango should not be insisting on trying to find a "Tibetan version" of > this character. It probably shouldn't even look for glyphs at all, but > instead always treat it as a zero-width character with no visible > glyph... but if it is going to use a glyph it should grab one from any > available font.
Hi, What font is it you're using? -- Cheers, Sven Arvidsson http://www.whiz.se PGP Key ID 760BDD22
signature.asc
Description: This is a digitally signed message part
