bounding_box() for t1 driver fonts was treating spaces as empty space
authorTony Cook <tony@develop=help.com>
Thu, 20 Jul 2006 13:42:04 +0000 (13:42 +0000)
committerTony Cook <tony@develop=help.com>
Thu, 20 Jul 2006 13:42:04 +0000 (13:42 +0000)
commit5eebac4253687ea12806ff6c11e8bcef612a8f2b
treee63425548efa9b0000526b2182ecdee194886ec3
parent6087ab23d39f032c8fa9a79d878422dc1dd862f2
bounding_box() for t1 driver fonts was treating spaces as empty space
when calculating the bounds, which they are, but this is inconsistent
with other drivers.  This was especially a problem for strings
containing only spaces where the left bound would end up far to the
right of the right bound, and similarly for the ascent and descent.

calculating the bounding box for an empty string invoked special
behaviour in t1lib, making it unreliable.

Fixes: http://rt.cpan.org/Ticket/Display.html?id=20555
MANIFEST
font.c
fontfiles/ExistenceTest.afm
fontfiles/ExistenceTest.pfb
fontfiles/ExistenceTest.sfd
fontfiles/SpaceTest.afm [new file with mode: 0644]
fontfiles/SpaceTest.pfb [new file with mode: 0644]
fontfiles/SpaceTest.sfd [new file with mode: 0644]
t/t30t1font.t