Bug 7427

Summary: DejaVu with bytecode interpretter enabled is too light
Product: DejaVu Reporter: Nicolas Mailhot <nicolas.mailhot>
Component: GeneralAssignee: Deja Vu bugs <dejavu-bugs>
Severity: normal    
Priority: high    
Version: unspecified   
Hardware: x86 (IA32)   
OS: Windows (All)   
i915 platform: i915 features:

Description Nicolas Mailhot 2006-07-05 01:49:38 UTC
dragoran at feuerpokemon dot de reported the following. Is it possible to make
DejaVu a td darker with the bytecode interpretter enabled ? (or at least make
autohinter and bytecode interpretter rendering match ?)

Nicolas Mailhot wrote:
> Dear Fedora user,
> A new font family is being proposed as the Fedora Core default. It
> probably impacts your language. Please tell us what you think about it:
> http://fedoraproject.org/wiki/Fonts/DejavuFeedbackCall
> Happy testing!

I tryed it but for me the default font used in apps (FC5) looks better 
and is easier to read...
the new fonts look to 'thin' and are harder to read because of this ..
1) I am using a TFT with a german locale + no subpixel AA, but greyscale AA
2) I have recompiled the freetypelib with the bytecode interpretter enabled
Comment 1 Ben Laenen 2006-07-05 05:12:16 UTC

I'm afraid making the glyph lines thicker not an option here. At the usual 
reading sizes, the stems will have a width of 1 pixel. Making that 2 pixels 
would make the glyphs look bold. (making the pixels darker cannot be done, 
stems should already be completely black)

Changing the width would also mean that all glyphs have to be tested again, 
and a lot of glyphs should be hinted again from scratch, which is too much 
work. And we also want to keep the Bitstream Vera look.

Maybe it just needs some time to get used to it? Most users who see the 
bytecode interpreter at work for teh first time say "that looks thin", but 
after one or two days they're used to it, and don't want to go back.
Comment 2 Ben Laenen 2006-07-05 07:26:16 UTC
resolving as WONTFIX

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.