90125 - Mozilla calculates text size wrong

Status: RESOLVED DUPLICATE of bug 63831

(Core :: Layout, defect)

Description

[Stanislav Malyshev]

When viewing http://www.livejournal.com/, mozilla renders the fonts in the wrong
way - text parts go one over other, and the text size is calculated incorrectly.
Font settings in prefs.js as follows:

user_pref("font.default", "sans-serif");
user_pref("font.name.cursive.x-cyrillic", "b&h-lucida console-iso8859-5");
user_pref("font.name.cursive.x-western", "adobe-courier-iso8859-1");
user_pref("font.name.fantasy.x-cyrillic", "b&h-lucida console-iso8859-5");
user_pref("font.name.fantasy.x-western", "adobe-courier-iso8859-1");
user_pref("font.size.fixed.x-western", 14);
user_pref("font.size.variable.x-cyrillic", 15);

Font path is:
/usr/X11R6/lib/X11/fonts/misc:unscaled,
/usr/X11R6/lib/X11/fonts/75dpi:unscaled,
/usr/X11R6/lib/X11/fonts/100dpi:unscaled,
/usr/X11R6/lib/X11/fonts/75dpi,
/usr/X11R6/lib/X11/fonts/100dpi,
/usr/X11R6/lib/X11/fonts/misc,
/usr/X11R6/lib/X11/fonts/Type1,
/usr/X11R6/lib/X11/fonts/Speedo,
/usr/X11R6/lib/X11/fonts/cyrillic,
/usr/X11R6/lib/X11/fonts/heb_type1,
/usr/X11R6/lib/X11/fonts/ttf,
/usr/share/fonts/default/Type1

If you need any more info, please ask. I will attach the screenshot of the
misrendered page.

Comment 1

[Stanislav Malyshev]

Attachment: misrendered www.livejournal.com

Comment 2

[Boris Zbarsky [:bzbarsky]]

Stanislav, are you using XFree 4.x?  If so, this is a duplicate of bug 63813
("PDT+ Linux: wrong width for 8 bit data rendered with 16 bit font") via bug
59915 ("Failing to calculate width of TrueType fonts on XFree 4.0")

Comment 3

[Stanislav Malyshev]

No, I have Xfree86 3.3.6. I noticed that the bug disappeared when I removed
encoding "iso10646-1" from my TTF fonts' fonts.dir. For what it worth. Still may
be linked to 8-bit/16-bit issues, maybe, since this encoding is Unicode?

Comment 4

[Boris Zbarsky [:bzbarsky]]

Er, I meant bug 63831.

Stanislav, could you try a July 10 nightly build with the iso10646-1 font
encoding in place to see whether the checkin for 63831 has fixed this bug?

Comment 5

[Boris Zbarsky [:bzbarsky]]

Stanislav, is this still a problem?

Comment 6

[Stanislav Malyshev]

Not checked yet, but bug 63831 looks like what I was seeing, so if it's fixed I
guess it should be OK. I'll try to check it soon anyway.

Comment 7

[Keyser Sose]

*** This bug has been marked as a duplicate of 63831 ***