Closed Bug 87886 Opened 24 years ago Closed 24 years ago

This page is incorret render

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED DUPLICATE of bug 78643

People

(Reporter: knutjbj, Assigned: karnaze)

References

(
URL
)

Details

IN this page text is wrapped around and is unreadable. I am using TimeNewroman and Ariel as standard fonts which are truetypes. My system is RedHat Linux 7.1 with XFree86 4.1. This page show perfect in Netscape 4.1
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.1+) Gecko/20010624 along with my fontlist. user_pref("intl.font_charset", "iso-8859-1"); user_pref("intl.font_spec_list", "misc-fixed-0-noscale-fixed-iso-8859-15,misc-fixed-0-noscale-prop-iso-8859-15,monotype-courier new-0-noscale-fixed-koi8-r,monotype-arial-0-noscale-prop-koi8-r,schumacher-clean-120-noscale-fixed-x-user-defined,schumacher-clean-120-noscale-prop-x-user-defined,nsPseudoFont-courier-100-noscale-fixed-UTF-8,nsPseudoFont-times-120-noscale-prop-UTF-8,isas-fangsong ti-120-noscale-fixed-gb_2312-80,isas-fangsong ti-120-noscale-prop-gb_2312-80,daewoo-gothic-0-noscale-fixed-ks_c_5601-1987,daewoo-gothic-0-noscale-prop-ks_c_5601-1987,misc-fixed-120-noscale-fixed-jis_x0201,misc-fixed-120-noscale-prop-jis_x0201,jis-fixed-120-noscale-fixed-jis_x0208-1983,jis-fixed-120-noscale-prop-jis_x0208-1983,adobe-courier-0-noscale-fixed-iso-8859-9,monotype-arial-0-noscale-prop-iso-8859-9,misc-fixed-0-noscale-fixed-iso-8859-7,misc-fixed-0-noscale-prop-iso-8859-7,monotype-courier new-0-noscale-fixed-iso-8859-5,monotype-arial-0-noscale-prop-iso-8859-5,misc-fixed-0-noscale-fixed-iso-8859-2,misc-fixed-0-noscale-prop-iso-8859-2,monotype-courier new-120-scale-fixed-iso-8859-1,monotype-times new roman-120-scale-prop-iso-8859-1,");
Probably a duplicate of bug 78643 via bug 59915
*** This bug has been marked as a duplicate of 78643 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
the fix for bug 63831 (now checked in) should fix this.
You need to log in before you can comment on or make changes to this bug.