Move weight after slant to match the order in cairo_select_font.

Added notes on DPI for image-based backends and on proposal for new cairo_text_glyphs function.
Added BUG about cairo_show_text not advancing the current point.
This commit is contained in:
Carl Worth 2004-04-02 08:01:09 +00:00
parent 72667ec568
commit b17b04aa38
4 changed files with 42 additions and 6 deletions

4
BUGS
View file

@ -48,4 +48,8 @@ to think about this in more detail.
--
cairo_show_text is not updating the current point by the string's advance values.
--
Caps are added only to the last subpath in a complex path.

View file

@ -1,3 +1,14 @@
2004-04-02 Carl Worth <cworth@east.isi.edu>
* src/cairo.h: Move weight after slant to match the order in
cairo_select_font.
* TODO: Added notes on DPI for image-based backends and on
proposal for new cairo_text_glyphs function.
* BUGS: Added BUG about cairo_show_text not advancing the current
point.
2004-03-30 Carl Worth <cworth@isi.edu>
* src/Makefile.am (libcairo_la_LIBADD): Add -lz.

22
TODO
View file

@ -5,6 +5,8 @@
* Make a more interesting PS backend, (other than the current
"giant-image for every page" approach).
* Figure out what to do with DPI for image/png backends.
* Change stroke code to go through one giant polygon. This will fix
problems with stroking self-intersecting paths.
@ -14,6 +16,26 @@ is done).
* Fix the intersection problem, (see reference to Hobby's paper
mentioned in cairo_traps.c).
* Add a new cairo_text_glyphs function (a sort of bridge between the
toy and the real text API):
> void
> cairo_text_glyphs (cairo_t *cr, const unsigned char *utf8,
> cairo_glyph_t *glyphs, int *num_glyphs);
>
> with num_glyphs as an input-output parameter. The behavior of this
> function would be such that calling:
>
> cairo_text_glyphs (cr, string, glyphs, &num_glyphs);
> cairo_show_glyphs (cr, glyphs, num_glyphs);
>
> would be equivalent too:
>
> cairo_show_text (cr, string);
>
> as long as the original size of glyphs/num_glyphs was large
> enough.
* Implement dashing for cairo_curve_to.
* Implement support for programmatic patterns, (ie. figure out how to

View file

@ -387,18 +387,17 @@ typedef struct {
double max_y_advance;
} cairo_font_extents_t;
typedef enum cairo_font_weight {
CAIRO_FONT_WEIGHT_NORMAL,
CAIRO_FONT_WEIGHT_BOLD
} cairo_font_weight_t;
typedef enum cairo_font_slant {
CAIRO_FONT_SLANT_NORMAL,
CAIRO_FONT_SLANT_ITALIC,
CAIRO_FONT_SLANT_OBLIQUE
} cairo_font_slant_t;
typedef enum cairo_font_weight {
CAIRO_FONT_WEIGHT_NORMAL,
CAIRO_FONT_WEIGHT_BOLD
} cairo_font_weight_t;
/* This interface is for dealing with text as text, not caring about the
font object inside the the cairo_t. */