I was getting my information from here:
http://www.freetype.org/freetype2/docs/tutorial/step2.html
http://www.freetype.org/freetype2/docs/tutorial/step2.html .
Thanks for your help, works now!
Werner LEMBERG wrote:
I would expect to get a character size around 1.0. For 'j' I get
0.485149
Hello together,
I am using freetype to load fonts and read vectorize them with
FT_Outline_Decompose.
I want to have exact controll over how many pixels the characters are in
height. The FT_Vector I get during decomposing I am dividing by
face-size-metrics.height and storing as a float.
I was
Werner LEMBERG wrote:
I am using freetype to load fonts and read vectorize them with
FT_Outline_Decompose.
I want to have exact controll over how many pixels the characters
are in height. The FT_Vector I get during decomposing I am dividing
by face-size-metrics.height and storing as
is that if you use
FT_Outline_Decompose() the scan-converter will always parse the outline
using the non-zero winding rule, whatever is the actual winding rule of
your font.
But may be I am wrong ?
Bertrand.
LonelyStar wrote :
Hello together,
I am trying to make Polygons for Fonts using
I just learned of FT_Outline_Decompose, which does the trick for me.
Thanks for the answer!
Nathan
Werner LEMBERG wrote:
If I understand the documentation correctly, the possible values in
the array outline-tags are FT_Curve_Tag_On, FT_Curve_Tag_Conic or
FT_Curve_Tag_Cubic.
ORed by
Hello together,
I am trying to make Polygons for Fonts using gluTesselator.
It works on many characters, but fails on characters with wholes.
So my guess is, that I use the wrong Winding rules. I set the winding this
way:
if(face-glyph-outline.flags | FT_OUTLINE_EVEN_ODD_FILL)
Hello together,
I have the problem that FT_Load_Glyph returns with error code 151 and I have
no Idea what that means.
How do I find out what a specific error code means?
Thanks!
Nathan
--
View this message in context:
http://www.nabble.com/Freetype-Error-codes.-tf2191132.html#a6063031
Sent
