Artifacts close to start/end points

[GoogleCodeExporter]

Freetype-go generates artifacts close to start and end path points,
output differs from Freetype-C.

Font is automatically converted from C to Q by FontForge, no problems detected.
Rearanged canonical start point to leftmost on the contour produces expected 
output.

Original issue reported on code.google.com by phil...@seznam.cz on 20 Feb 2015 at 9:48

Attachments:

• ftError.ttf
• out.png
• main.go

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Reduced artifact example mapped to "1", and correct to "0" with start on the 
leftmost contour point.
This is tolerated by freetype-C.

Original comment by phil...@seznam.cz on 21 Feb 2015 at 12:48

Attachments:

• ftError.ttf
• out.png

[GoogleCodeExporter]

Aforementioned problem is due to freetype-go assumes first path point as 
on-curve one.

Please see my proposed rewrite of drawContour() in 
code.google.com/p/freetype-go/freetype/freetype.go, it is almost camelcased 
FT_Decompose_Curve function.
It can be tested with attached font for on-on, on-off, off-on and off-off 
first-last curve points, mapped to 0-3.

Original comment by phil...@seznam.cz on 23 Feb 2015 at 9:25

Attachments:

• ftTest.ttf
• drawContour.go

[GoogleCodeExporter]

This issue was closed by revision 46c3056cafbb.

Original comment by nigel...@golang.org on 9 Mar 2015 at 12:32

• Changed state: Fixed