Bug 112879
| Summary: | Mozilla should be compiled with freetype enabled for a better printint | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jungshik Shin <jshin> |
| Component: | mozilla | Assignee: | Christopher Blizzard <blizzard> |
| Status: | CLOSED WONTFIX | QA Contact: | Ben Levenson <benl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1 | CC: | aleksey, chpe, jfrieben, mitr, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-02-12 18:39:40 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jungshik Shin
2004-01-05 09:20:34 UTC
Nope, I'm not going to enable the freetype code in our builds. How about reconsidering enabling "FreeType2" in the "mozilla" builds? Fedora browsers still only offer plain PS fonmt printing. "Xprint" has also been discarded by the Red Hat developers. This makes life sort of difficult. In the past, I built my own "xorg-x11-Xprint" packages, but now that e.g. "epiphany" does not even use the "mozilla" printing backend anymore, one hardly knows ewhat to do. When "Xprint" support got declined, Red Hat developers stressed, that they were pursuing an alternative solution. This must have been about 2 years ago :( There's absolutely no need to enable freetype for a better printing quality because I greatly improved Mozilla's PS printing. There's little need for Xprint. I can't imagine any text that can be rendered better with Xprint than with the current Mozilla printing engine. See https://bugzilla.mozilla.org/show_bug.cgi?id=234182 I want to be able to print web pages using "Truetype" fonts as they are rendered on-screen. In the case of "mozilla", this works for me when "xprint" is enabled, and an "xprint" server is installed and running as well as the required "TrueType" fonts. An "epiphany" developer suggested to rebuild "mozilla" with "--enable-freetype2" to obtain "TrueType" fonts printing for newer releases of "epiphany" that rely on "libgnomeprint[ui]". Right now, "epiphany" (based upon "mozilla") falls back to plain "PostScript" fonts# which is undesirable. I don't what's going on with Epiphani. Anyway, they're downright wrong. There's absolutely no need to enable freetype2 to print with **truetype** fonts. PLEASE, read what's done at mozilla bug 234182 !!! There WAS a reason for me to burn a lot of candles 'killing' quite a lot of trees and printer ink. The print quality of firefox 1.5.x with the PS engine that *embeds* truetype glyphs (after converting them to PS type 1 outlines) is a lot better (in terms of WYSWYG and other aspects) than the print quality obtained with Xprint that relies on 20-year old XLFD. Thanks for your comment. To be honest, I do not have "firefox" installed on my system. On "Fedora Core", "epiphany" is built against plain "mozilla" and requires this package to be installed. For your information, here my bug report for "epiphany": http://bugzilla.gnome.org/show_bug.cgi?id=323892 The patch from mozilla bug https://bugzilla.mozilla.org/show_bug.cgi?id=234182 is not present in mozilla 1.7 which is what FC *still* inflicts on their gecko embedders. (In reply to comment #7) > is not present in mozilla 1.7 which is what FC *still* inflicts on their gecko > embedders. Given the above, Joachim, what you can do is to file a new FC bug for upgrading to Gecko 1.8 which is used by Firefox 1.5/Seamonkey 1.0/Thunderbird 1.5 |