On Sun, Oct 26, 2008 at 05:22:57PM -0400, Eric Dorland wrote: > * Rich Felker ([EMAIL PROTECTED]) wrote: > > Package: iceweasel > > Version: 2.0.0.6-1 > > Severity: normal > > Tags: l10n > > > > *** Please type your report below this line *** > > > > When using the "Tibetan Machine Uni" font (which is packaged with > > Debian and intended as the default font for Tibetan script), Iceweasel > > is displaying every combining character separately as a dotted circle > > with the combining character attached to it, rather than correctly > > attached to the previous character. See screenshot: > > > > http://www.aerifal.cx/~dalias/images/iceweasel_tmuni_bug.png > > > > And what it should look like (using a different font): > > > > http://www.aerifal.cx/~dalias/images/iceweasel_jomo_ok.png > > > > Pango is enabled; it is required for display of Tibetan text. This > > does not seem to be a bug in Pango, however, since both GTK widgets > > and GIMP successfully render Tibetan text using Pango. On the other > > hand, it very likely could be a misuse of Pango, since Abiword > > exhibits incorrect display (albeit different from the Iceweasel issue; > > Abiword seems to ignore the OpenType tables completely) with this font > > as well, while working fine with other fonts. > > > > As a workaround, users can remove the ttf-tmuni package and install > > the ttf-dzongkha package instead, which provides a different font for > > Tibetan script. However, users of these languages will often want to > > have all Tibetan fonts installed for word processing use, etc., which > > will cause any website explicitly requesting the "Tibetan Machine Uni" > > font to become completely illegible. > > Did Iceweasel 3.0 fix the problem?
Yes; I simply had not noticed since I had upgraded to a newer version of the Tibetan Machine Unicode font which avoids the problem. (The newer version is designed to support Windows 2k/XP machines without up-to-date Uniscribe by using simpler OpenType features. ttf-tmuni package should be updated to use this newer version too, but that's a separate issue report I suppose..) Thanks for checking back in. You can close this bug. Rich -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
