diff options
| author | Adrian Johnson <ajohnson@redneon.com> | 2008-04-05 21:15:15 +1030 |
|---|---|---|
| committer | Adrian Johnson <ajohnson@redneon.com> | 2008-04-06 00:36:02 +1030 |
| commit | 03d2b098ff245ff6724b1d83a121f5ce9dcd0b51 (patch) | |
| tree | 66d268c1d6dae556c912fb542fe393256aaabd38 /src/cairo-type1-fallback.c | |
| parent | 40cee8c57879d37d77c5a93de8f7bdef28851923 (diff) | |
| download | cairo-03d2b098ff245ff6724b1d83a121f5ce9dcd0b51.tar.gz | |
Type1-fallback: Use correct glyph advance in Type 1 charstrings
5050c55f93af fixed type1-fallback to use the glyph advance instead of
glyph width in the stored glyph metrics in the font. However it did
not fix the same bug in Type 2 charstrings (used by CFF fallback in
PDF). This problem was not noticed since the glyph widths in the PDF
font dictionary overrides these values.
Fix this in case any software reading cairo PDFs uses these values.
Diffstat (limited to 'src/cairo-type1-fallback.c')
| -rw-r--r-- | src/cairo-type1-fallback.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/cairo-type1-fallback.c b/src/cairo-type1-fallback.c index a0fe5da6c..0d81ccb5f 100644 --- a/src/cairo-type1-fallback.c +++ b/src/cairo-type1-fallback.c @@ -411,7 +411,7 @@ cairo_type1_font_create_charstring (cairo_type1_font_t *font, path_info.current_x = (int) scaled_glyph->metrics.x_bearing; path_info.current_y = (int) scaled_glyph->metrics.y_bearing; } else { - charstring_encode_integer (data, (int) scaled_glyph->metrics.width, type); + charstring_encode_integer (data, (int) scaled_glyph->metrics.x_advance, type); path_info.current_x = 0; path_info.current_y = 0; |