I've noticed you changed the filename of the example to
example4.cpp, you should modify the include directive at the end of
the file too to be able to build it. The generated file will be
called example4.moc in this case. So this line:
#include main.moc
should be changed to
In October I wrote:
I have tested it and it works. All the glyphs rendered with
FT_RASTER_FLAG_DIRECT flag look the same as if they were rendered
onto a bitmap.
Unfortunately, this isn't true. Compiling the attached example4.cpp
and comparing
./example4
When rendering glyphs with cff outlines (otf, pfb fonts) the
control points which are located under the baseline are
connected with straight lines, for ttf fonts all the glyphs are
rendered correctly. This problem occurs only when I use direct
rendering with the FT_RASTER_FLAG_DIRECT
I think I've found a bug in the cff renderer algorithm or I'm doing
something seriously wrong. When rendering glyphs with cff outlines
(otf, pfb fonts) the control points which are located under the
baseline are connected with straight lines, for ttf fonts all the
glyphs are rendered
Uf, sorry, it seems that the download link have timed out.
So this http://www.filefactory.com/file/b36458b/n/renderer_problem.zip is
the example app, and
thishttp://www.filefactory.com/file/b36458c/n/letter_g.pngis how FT
renders glyphs.
On Fri, Sep 10, 2010 at 11:55 AM, Róbert Márki
Uf, sorry, it seems that the download link have timed out. So
this
http://www.filefactory.com/file/b36458b/n/renderer_problem.zip is
the example app, and this
http://www.filefactory.com/file/b36458c/n/letter_g.png is how FT
renders glyphs.
Will have a look soon.
Werner
Hi everyone!
I think I've found a bug in the cff renderer algorithm or I'm doing
something seriously wrong.
When rendering glyphs with cff outlines (otf, pfb fonts) the control points
which are located under the baseline are connected with straight lines, for
ttf fonts all the glyphs are rendered
