freetype
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ft] ugly output with freetype and gtk


From: suzuki toshiya
Subject: Re: [ft] ugly output with freetype and gtk
Date: Tue, 17 Jan 2012 22:57:00 +0900
User-agent: Mozilla-Thunderbird 2.0.0.12 (X11/20080406)

Hi,

Thank you for reporting with illustrative screenshot.

Your screenshot does not seem to be hinting issue, rather,
it looks like something wrong in the rasterization itself,
forced to say, integer overflow etc. The noise pixel on
glyph "d" seem to lack reasonable cause in hinting.

I want to know if any smallest rasterization program, like,
ftview (a demo program in freetype2-demos) can show same
issue or not. If you cannot execute such program on your
embedded system, please let me know what kind of testing
progam can be executed on your system.

Also I'm interested in the noise pixels are exactly
reproduceable, or, they appear at different positions
when you reboot the system.

Talking about my personal experience, some old rogue
FreeType2 client breaks the cached glyph bitmap, so
same glyphs shown in one execution have constant noises
(in your screenshot, "e", "g", "n", "u" have constant
noise pixels), but when I terminate/restart the program,
the noise pixels appear differently.

Regards,
mpsuzuki

Jochen Jägers wrote:
Hello,

i'm developing an embedded system for home automation based on
gnu/linux.

The userinterface is build in HTML/Javascript displayed in a fullscreen
browser based on webkit-gtk with freetype as font-backend.

I get ugly output on some glyphs. I've made a screenshot to illustrate
this ugly output.
http://tinypic.com/r/4uwbkl/5

Look at "Standort" for example. The "d" has two pixels in the top left
corner. I get this ugly output with different types and different file
formats. The text in other gtk-based applications look ugly too.

I've tryed many things i found on the internet like different settings
for hinting, lcdfilter and subpixels but nothing worked.

I've also tryed different versions of freetype (2.4.4 and 2.4.8) with
the same ugly result.

At the moment I've no idea to solve this problem.
Do you have any idea what i can try?

Greetings
Jochen Jägers


_______________________________________________
Freetype mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/freetype




reply via email to

[Prev in Thread] Current Thread [Next in Thread]