Closed
Bug 150519
Opened 23 years ago
Closed 23 years ago
Search results from http://www.google.co.il/ print in horrible quality
Categories
(Core Graveyard :: Printing: Xprint, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.0.1
People
(Reporter: roland.mainz, Assigned: roland.mainz)
References
()
Details
Attachments
(1 file, 3 obsolete files)
1.40 KB,
patch
|
shanjian
:
review+
jst
:
superreview+
jesup
:
approval+
|
Details | Diff | Splinter Review |
Trying to print http://www.google.co.il/search?q=mozilla&hl=iw looks horrible
since it seems to pick mainly one of these two fonts to render the results:
-misc-fixed-medium-r-semicondensed--0-0-75-75-c-0-iso8859-1
-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1
The problem is burried in the detail that the page _forces_ the use of the
-*--*-*-*-*-c-*-* fonts.
Assignee | ||
Comment 1•23 years ago
|
||
Taking myself...
Assignee: katakai → Roland.Mainz
QA Contact: Roland.Mainz → katakai
Assignee | ||
Comment 2•23 years ago
|
||
Upcoming patch was created after applying patch from bug 148470 ('Ban "-dt-*"
(bitmap!!) fonts from Xprint') and needs working Xprint font banning code (bug
148468 - 'Xprint-specific X font banning code is broken') ...
Assignee | ||
Updated•23 years ago
|
Summary: http://www.google.co.il/ results print in horrible quality → Search results from http://www.google.co.il/ print in horrible quality
Assignee | ||
Comment 3•23 years ago
|
||
Assignee | ||
Comment 4•23 years ago
|
||
Another - better solution may be to find PS Type1 version of the "-c-" fonts...
however a Google search indicated that there is no such font... ;-(
Assignee | ||
Comment 5•23 years ago
|
||
shanjian:
Can you r= the patch, please ?
Assignee | ||
Comment 6•23 years ago
|
||
Comment on attachment 87067 [details] [diff] [review]
Patch for 2002-06-07-08-trunk, ban all fonts with *--$(number>0)-$(number>0)-$(number>0)-$(number>0)-c-*
Patch needs minor adjustments since iz bans all fonts from
/usr/openwin/lib/locale/ja/X11/fonts/75dpi/ ... ;-(
Attachment #87067 -
Flags: needs-work+
Assignee | ||
Comment 7•23 years ago
|
||
I am limiting the ban now to iso8859-* encodings since they have tons of other
fonts which fit here "better".
Non iso8859-* still can use all *-c-* bitmap fonts fonts...
Note that the patch does not affect outline-scaleable fonts, this patch bans
only bitmap fonts...
Attachment #87067 -
Attachment is obsolete: true
Comment 8•23 years ago
|
||
Roland,
You might want to limit you banned list within iso8859-* as well. iso8859-1
fonts are abundant. Things are probably for iso8859-2 (east european). Other
than that, I have no idea.
BTW, if the fonts in your rejected list are the only fonts available for certain
encoding, are those fonts still rejected?
Assignee | ||
Comment 9•23 years ago
|
||
Shanjian Li wrote:
> You might want to limit you banned list within iso8859-* as well. iso8859-1
> fonts are abundant. Things are probably for iso8859-2 (east european). Other
> than that, I have no idea.
The new patch (attachment 87125 [details] [diff] [review]) contains already such a "ban" which is limited
to the iso8859-[0123456789]* fonts (otherwise we ban the janapese 75DPI bitmap
fonts on Solaris (which is bad on Solaris 2.7 since it does not come with other
fonts for japanese)).
Or do you mean I should restrict the ban in a further way ?
> BTW, if the fonts in your rejected list are the only fonts available for
> certain encoding, are those fonts still rejected?
Our X font ban's are final. They are banned forever.
Comment 10•23 years ago
|
||
Yes, that's what I mean. For example, iso8859-11 is Thai, and I believe very few
fonts available, even fewer than japanese. So you might want to do the same
thing to this encoding as well. Since your ban is final, I would suggest to ban
iso8859-1, iso8859-2, iso8859-15. Don't ban other encoding until we hear
complaints.
Assignee | ||
Comment 11•23 years ago
|
||
Shanjian Li wrote:
> Don't ban other encoding until we hear complaints.
Agreed... :)
Assignee | ||
Comment 12•23 years ago
|
||
More fun... further testing shows that our code treats the -misc-fixed-* bitmap
fonts as outline-scaleable fonts (!!) and therefore bypasses all
tricks&safeguards which should prevent scaleable bitmap fonts (even bug 148690
'RFE: For Xprint force use of outline scaleable fonts if possible') ... ;-(
Assignee | ||
Comment 13•23 years ago
|
||
Very simple issue:
The code which looks for printer-builtin fonts is slightly wrong.
Attachment #87125 -
Attachment is obsolete: true
Assignee | ||
Comment 14•23 years ago
|
||
Attachment #87194 -
Attachment is obsolete: true
Assignee | ||
Comment 15•23 years ago
|
||
Sorry for my wrong assumtions in the previous comments... looks I was trying to
cure the symptoms and not the root of the problem... ;-(
----
Requesting r=/sr= ...
Comment 16•23 years ago
|
||
Comment on attachment 87195 [details] [diff] [review]
Better patch for 2002-06-07-08-trunk to kill the root of the bitmap-font-evilness and updating the comment about printer-builtin fonts
r=shanjian, simple is better, and more likely to reveal the truth.
Attachment #87195 -
Flags: review+
Comment 17•23 years ago
|
||
Comment on attachment 87195 [details] [diff] [review]
Better patch for 2002-06-07-08-trunk to kill the root of the bitmap-font-evilness and updating the comment about printer-builtin fonts
sr=jst
Attachment #87195 -
Flags: superreview+
Assignee | ||
Comment 18•23 years ago
|
||
Removing dependicy on bug 148468 and bug 148470 since the new patch does not
require them...
Assignee | ||
Updated•23 years ago
|
Blocks: xprint_machv
Comment 19•23 years ago
|
||
Checked in to trunk for Roland
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•23 years ago
|
Keywords: mozilla1.0.1
Updated•23 years ago
|
Attachment #87195 -
Flags: approval+
Comment 21•23 years ago
|
||
Comment on attachment 87195 [details] [diff] [review]
Better patch for 2002-06-07-08-trunk to kill the root of the bitmap-font-evilness and updating the comment about printer-builtin fonts
Approved for 1.0 branch. Please remove mozilla1.0.1+ when it's fixed and add
fixed1.0.1
Updated•23 years ago
|
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•