Re: [ft] ugly output with freetype and gtk

2012-01-17 Thread suzuki toshiya
Hi, Hmm, if ftview could not reproduce the noise pixel, the next library to be checked would be Pango (text rendering engine of GTK+) or Cairo (the vector graphic engine used by Pango, under some configuration). However, yet I don't know which display subsystem is used in your embedded systems (

Re: [ft] ugly output with freetype and gtk

2012-01-17 Thread Jochen Jägers
Hi, thank your for your fast answer. With ftview everthing looks fine so it seems to be a gtk problem. The noise pixels are exactly reproduceable. After reboot and also after reinstalling the whole system the noise pixels are at the same position. only by changing fontconfig parameters like hinti

Re: [ft] [ft-devel] FreeType License and patents

2012-01-17 Thread Dave Crossland
On 17 January 2012 09:25, David Turner wrote: > An easier approach would be to ask for all future contributions to be > covered by "FreeType License 1.1", > ... >> Apache2 is not compatible with GPLv2 notably because of this >> particular patent clause (that's the general agreement anyway -- some

Re: [ft] ugly output with freetype and gtk

2012-01-17 Thread suzuki toshiya
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 k

Re: [ft] ugly output with freetype and gtk

2012-01-17 Thread Werner LEMBERG
> I get ugly output on some glyphs. [...] > > 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. This is not sufficient information

[ft] ugly output with freetype and gtk

2012-01-17 Thread Jochen Jägers
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 out

Re: [ft] [ft-devel] FreeType License and patents

2012-01-17 Thread David Turner
Hello, Just to make it clear, I'm too in favor of adding an Apache2-like patent clause to the license. And for the sake of full-disclosure, my employer does releases quite a large amount of Apache-2 licensed code. On Fri, Jan 13, 2012 at 8:34 PM, Eric Rannaud wrote: >

Re: [ft] FreeType License and patents

2012-01-17 Thread Werner LEMBERG
Comments? >>> >>> Why not just switch to Apache? Well, we have our special advertisement clause, and I would like to stay with it. >> However, by switching to Apache2, or by adding such a clause, you >> will likely make Freetype harder to use for some projects that may >> have liked the curr

Re: [ft] [ft-devel] FreeType License and patents

2012-01-17 Thread Werner LEMBERG
> Are you willing to do the work to make sure no FreeType contributor > currently has a patent on code they have contributed? This should be doable, given that there are just a handful of contributors who added longer, non-trivial stuff. Werner