Re: [ft-devel] [patch] emboldening rework v1

2012-04-19 Thread Alexei Podtelezhnikov
On Wed, Apr 18, 2012 at 2:18 PM, Werner LEMBERG w...@gnu.org wrote: FT_ORIENTATION_NONE is supposed to mean CANNOT BE DETERMINED, which is easier said than done. Any contour has a well defined orientation as a sign of the area it covers: plus or minus. It is only the degenerate contours or the

[ft-devel] On contour directions and fill rules (was Re: [patch] emboldening rework v1)

2012-04-19 Thread Behdad Esfahbod
Ok, I *was* seriously misguided. I think I understand things now. Let me summarize for posterity. What puzzled me before is that I came across fonts that have both TrueType orientation and Type1 orientation in the same glyph (but separate from eachother), and FreeType handles them fine. It

Re: [ft-devel] On contour directions and fill rules

2012-04-19 Thread Werner LEMBERG
A small remark: - No self-intersection. Now, when one says self-intersecting, one has to qualify. I was under the impression that assuming outlines are not self-intersecting was a safe assumption. However, I'm convinced now that this is absolutely false assumption. Yep. I'd say

Re: [ft-devel] On contour directions and fill rules

2012-04-19 Thread Behdad Esfahbod
On 04/19/2012 03:11 PM, Werner LEMBERG wrote: A small remark: - No self-intersection. Now, when one says self-intersecting, one has to qualify. I was under the impression that assuming outlines are not self-intersecting was a safe assumption. However, I'm convinced now that this is

Re: [ft-devel] On contour directions and fill rules

2012-04-19 Thread Werner LEMBERG
It competes with freetype-gl really. It's a GPU rasterizer. The main different with freetype-gl is that I don't do any sampling, so the glyphs are truly infinitely zoomable. Nice! No time to look at it more closely, but I've recently skimmed over a paper which uses wavelet transformation