Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=473836
Orion Poplawski <orion(a)cora.nwra.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|orion(a)cora.nwra.com |
--- Comment #27 from Orion Poplawski <orion(a)cora.nwra.com> 2008-12-10 10:37:11 EDT ---
Can we please get this assigned to the proper component (and get me out of the
loop)?
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=473836
Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|nicolas.mailhot(a)laposte.net |
--- Comment #26 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> 2008-12-10 10:28:20 EDT ---
I've seen the screenshots.
They don't correspond to my own preferences as displayed on my hardware (the
rendering on another screen may be different depending on pixel density, RVB
repartition, gamma settings, etc).
However as I wrote before those preferences are subjective and if there is one
thing I've learnt since working on fonts is that if you show 3 different
screenshots to three different people they'll all choose a different one as the
crapiest and will be convinced the two others share their POW.
So that's not conclusive.
Post a screenshot of what you consider good and people like Behdad may tell you
how to achieve this kind of rendering. I've stopped playing this game long ago.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=473836
--- Comment #25 from Andrzej Nowak <epsilon(a)loiv.torun.pl> 2008-12-10 10:10:41 EDT ---
I see your point, however it most likely is not my case that you are writing
about.
With all due respect, ever since I have filed this bug I have been treated like
a novice. Please look again at the screenshots I've attached. The hardware
correctly displays incorrect rendering, the hard evidence is on the images,
which are screenshots, not photographs of my screen, so they look the same on
any reasonable screen or graphics card.
I highly doubt that the rendering visible on my screenshots is intentional to
make up for hardware deficiencies, and if it is, the software incorrectly
recognizes the hardware as deficient.
Changing any setting - be it DPI, antialiasing, pixel order, font smoothing -
yields worse results. Trust me, I've experimented with that a lot before
deciding to bother people here at bugzilla, who already have a lot of other
stuff to worry about.
Both systems I own have exactly the same font settings, although the hardware
configurations are different, and that's because they give the best results. On
both systems fonts look perfectly fine in MS Windows and Fedora 6 and Fedora 7,
however on one of them Fedora 10 displays crap. Therefore, although I am aware
that this might not be the case, I trust that there is no problem with my
hardware (which is, on a side note, definitely not low end).
In essence, a fresh install of Fedora is nearly unusable for me because of this
issue and I am willing to help you make it better, so that less people
experience the problem. But I need assistance with that.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=473836
Nicolas Mailhot <nicolas.mailhot(a)laposte.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nicolas.mailhot(a)laposte.net
--- Comment #24 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> 2008-12-10 09:09:48 EDT ---
That's something else entirely, if the whole system behaves the same way,
everything is probably working fine.
Font settings are highly subjective, their effects depend on the hardware you
have, and what's best for one font won't necessarily be best for another, so
two different systems, with different hardware, and defaults from different
years, behaving differently, is most definitely NOTABUG.
If you prefer the old defaults you just have to copy them from the old system
to the new one. Note however that unless the hardware is identical there is no
warranty you'll find them as satisfying on one system compared to the other.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.freedesktop.org/show_bug.cgi?id=13416
--- Comment #7 from Julian Sikorski <belegdol(a)gmail.com> 2008-12-10 05:26:39 PST ---
Please have a look into this issue, no document using Arial Narrow font can be
displayed properly at this point. It's likely that in order to fix this
properly bug #18725 will have to be fixed first.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=473836
Andrzej Nowak <epsilon(a)loiv.torun.pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Fonts in firefox look |Fonts in GNOME look blurry
|blurry |(was: "in Firefox")
--- Comment #23 from Andrzej Nowak <epsilon(a)loiv.torun.pl> 2008-12-10 07:47:08 EDT ---
Nicolas, please note that in recent updates I've also attached screenshots of
other Gnome applications which are affected, the problem is not Firefox
specific, however it is best visible in Firefox.
However, you still might be right. I'm not closely familiar with the structure
of the font subsystem in Gnome.
More importantly, I have another system, a FC7 upgraded to FC10 and everything
is fine there - fonts are less crisp than in MS Windows, but much better than
on the attached screenshots and they're perfectly fine for daily usage. I don't
understand where this difference in rendering comes from, since the system with
the clean install is the one with the problems.
If this is not a freefont problem, where should this be reported?
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=473836
--- Comment #22 from Nicolas Mailhot <nicolas.mailhot(a)laposte.net> 2008-12-10 07:25:42 EDT ---
The reporter writes that the same fonts work fine in the rest of the desktop
gui, that also uses the system freetype with autohinting.
Thus clearly the problem is not the system freetype or cairo libs, the problem
lies in the way firefox uses them. Investigation will probably show that:
1. firefox fails to pass a crucial rendering parameter to one of the system
libs, or
2. that since firefox insists on duplicating a private font configuration
system in prefs.js (instead of using the desktop settings broadcasted via
XSettings), it's missing one parameter which had been set desktop-side and not
duplicated by the user manually in prefs.js.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=473836
Ben Laenen <bl.bugs(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bl.bugs(a)gmail.com
--- Comment #21 from Ben Laenen <bl.bugs(a)gmail.com> 2008-12-10 07:10:38 EDT ---
Maybe you should get a copy of freetype that has the bytecode interpreter
enabled so you don't have to use the freetype autohinter anymore. Using the
truetype hinting instructions from the font itself will make it much more
crisp.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=475593
--- Comment #5 from Orcan 'oget' Ogetbil <orcanbahri(a)yahoo.com> 2008-12-10 02:53:37 EDT ---
(In reply to comment #4)
> (In reply to comment #3)
> > * Packages must not own files or directories already owned by other packages.
> > The directories:
> > /usr/share/fonts.
> > /etc/fonts/conf.d
> > are already owned by filesystem and fontconfig. Why share the ownership?
>
> As posted on the guideline change plan they will be removed from those other
> packages after this one is available to keep font policy in a single place.
>
Sorry, I missed that part.
> > - Suggestion: Since you are the upstream, you can provide a Makefile in the
> > source so that you don't have to do those tricks in the SPEC file.
>
> You'll find out that to keep directory info in a single place, the macro file,
> you'd need to play rpm tricks in this Makefile, and at this point it's stupid
> to do it out of rpm spec space
>
It was just my suggestion and I respect your decision. I'll approve the package
as soon as I see the official FPC announcement.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.