The previous "the endpoints are inclusive" comment seems confusing. It's true
that the bounding box's max X equals the right-most coordinate, which suggests
<= instead of <, but that node's coordinate is itself exclusive. Consider the
solid 1-pixel square: (0, 0), (64, 0), (64, 64), (0, 64) in fixed.Point26_6
coordinates. The right-most coordinate is 64, and the bounding box's max X
equals 64, but rasterizing that square only affects sub-pixels up to but not
including 64.
Instead, it seems accurate to follow the fixed.Rectangle26_6 description, in
that the max values are exclusive.
just version 2. The FTL (Freetype Licence) is still available. This
matches the original Freetype library (written in C).
This only expands and does not further restrict the licensing options
available to users of the freetype-go library.
R=adg
CC=golang-dev
http://codereview.appspot.com/1731049
draw text onto an image.
This is a simple API that doesn't handle line breaking, ligatures,
right-to-left or vertical scripts, and other fancy features.
R=r, rsc
CC=golang-dev
http://codereview.appspot.com/1121045
Parsing a malformed TTF may result in an index out-of-bounds panic,
rather than guaranteeing to return an error. This may be tightened
in the future.
R=r, rsc
CC=golang-dev
http://codereview.appspot.com/940044
