The attached patch returns the error code 0xFF when the margin is
crossed and leaves 3 pixels blank at the right margin.
I've just tested it, and it fails for fonts which can't be emboldened
(for example, BDF). Besides that, it looks OK.
Werner
inline:
On Tue, Jul 3, 2012 at 6:08 PM, Werner LEMBERG w...@gnu.org wrote:
The attached patch returns the error code 0xFF when the margin is
crossed and leaves 3 pixels blank at the right margin.
I've just tested it, and it fails for fonts which can't be emboldened
(for example, BDF). Besides that,
On Wed, Jun 27, 2012 at 1:22 PM, Werner LEMBERG w...@gnu.org wrote:
[...] the drawing functions ultimately inherit the error codes from
FT_Glyph_To_Bitmap currently. Therefore it has to be something
different from those defined in fterrdef.h to distinguish. It would
be good if freetype
The attached patch changes the way 'ftview' fills the window with
glyphs so that the right margin is less blank and a larger number of
glyphs shown. It uses the actual width of the current grBitmap,
instead of super conservative max_advance, when fitting the glyphs
in the available space.
The attached patch changes the way 'ftview' fills the window with
glyphs so that the right margin is less blank and a larger number of
glyphs shown. It uses the actual width of the current grBitmap,
instead of super conservative max_advance, when fitting the glyphs
in the available space.
I've picked FT_Err_Raster_Overflow to indicate the boundary. Is
that appropriate?
No, it isn't IMHO: FT_Err_Raster_Overflow is a fatal error, indicating
a serious problem which the rasterizer can't manage. I think a simple
integer will serve as return error instead of FT_Error.
I am also
On Wed, Jun 27, 2012 at 8:33 AM, Werner LEMBERG w...@gnu.org wrote:
I've picked FT_Err_Raster_Overflow to indicate the boundary. Is
that appropriate?
No, it isn't IMHO: FT_Err_Raster_Overflow is a fatal error, indicating
a serious problem which the rasterizer can't manage. I think a simple
[...] the drawing functions ultimately inherit the error codes from
FT_Glyph_To_Bitmap currently. Therefore it has to be something
different from those defined in fterrdef.h to distinguish. It would
be good if freetype reserved an FT_Err_User, defined as -1 or 0xFF
perhaps, which is not
In memory of Paul Alexi
Hi all,
The attached patch changes the way 'ftview' fills the window with
glyphs so that the right margin is less blank and a larger number of
glyphs shown. It uses the actual width of the current grBitmap,
instead of super
