golang-freetype/truetype
Nigel Tao 3cc748686b Use fixed.Rectangle26_6 instead of truetype.Bounds.
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.
2015-08-30 22:06:37 +10:00
..
face_test.go Quantize sub-pixel glyph rendering. 2015-08-25 22:34:31 +10:00
face.go Use fixed.Rectangle26_6 instead of truetype.Bounds. 2015-08-30 22:06:37 +10:00
glyph.go Use fixed.Rectangle26_6 instead of truetype.Bounds. 2015-08-30 22:06:37 +10:00
hint_test.go Use the fixed.Int26_6 type in package truetype. 2015-08-18 16:30:37 +10:00
hint.go Delete the f26dot6 type in favor of fixed.Int26_6. 2015-08-18 16:47:46 +10:00
opcodes.go Move files up one level. 2015-08-12 14:30:01 +10:00
truetype_test.go Use fixed.Rectangle26_6 instead of truetype.Bounds. 2015-08-30 22:06:37 +10:00
truetype.go Use fixed.Rectangle26_6 instead of truetype.Bounds. 2015-08-30 22:06:37 +10:00