this doesnt apply to current fontconfig anymore from what i see. let me
know if thats wrong.
** Changed in: fontconfig (Ubuntu)
Status: Confirmed => Invalid
--
fontconfig don't use autohinter as default
https://bugs.launchpad.net/bugs/14310
You received this bug notification because you a
** Changed in: fontconfig (Ubuntu)
Assignee: Michael Vogt (mvo) => (unassigned)
--
fontconfig don't use autohinter as default
https://bugs.launchpad.net/bugs/14310
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs maili
Thus far, nobody has ever been sued for these patents. (At least not as
far as I know.)
And the bytecode interpreter dramatically improves font rendering for
all good quality fonts.
When a font looks worse with the bytecode interpreter enabled, it means
it's a crappy font! It's either has no hint
Per the Freetype.org developers the "bytecode interpreter" is not to be used by
any distribution because of the TrueType patents held by Microsoft and Apple.
Mr. Shuttleworth's blog does not address the patent issues on the bytecode
interpreter.
Does Ubuntu pay for the license for all the users o
Status: New -> Confirmed, based on comments.
** Changed in: fontconfig (Ubuntu)
Status: New => Confirmed
--
fontconfig don't use autohinter as default
https://bugs.launchpad.net/bugs/14310
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscr
** Changed in: fontconfig (Ubuntu)
Status: Confirmed => New
--
fontconfig don't use autohinter as default
https://bugs.launchpad.net/bugs/14310
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bug
It seems that, in common usage, the autohinter ought to at least be enabled for
the default fonts used in Ubuntu (Vera Sans/Vera Serif)
as it makes them look MUCH better. The above-mentioned Ubuntu/Fedora
comparison does a good job of showing this... Granted, some fonts may look
worse with the
I guess I was mistaken; I thought I remembered reading a while back that
autohinter was enabled by default. What is with the delay in putting
this into effect? Has anyone had negative effects from enabling this?
--
fontconfig don't use autohinter as default
https://bugs.launchpad.net/bugs/14310
Y
Hi, I read the recent font discussion at Mark Shuttleworth's blog that
said autohinter is disabled by default in Debian and Ubuntu, vs. Fedora,
interesting post: http://www.markshuttleworth.com/archives/119
"I also do the “no hinting” thing in GNOME. The thing I don’t get is the
difference in font
Brian, are you sure autohinter is enabled by default? In Ubuntu 7.04, I
think I still see a positive difference after enabling it through
fontconfig-config. So if it's not enabled by default, I hope it will be
considered for gutsy.
Another interesting bug concerning autohinter is "Desktop UI for e
I think this bug can be closed. It is old and autohinter was enabled by
default a while ago.
--
fontconfig don't use autohinter as default
https://bugs.launchpad.net/bugs/14310
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bu
the autohinter significantly degrades the appearance of known fonts such
as tahoma, verdana, arial, etc. using bci is crucial for these fonts, as
they are barely recognizeable at lower point sizes.
besides, since a few weeks, autohinting seems to be enabled by default
in ubuntu 6. i don't know wha
12 matches
Mail list logo
