Re: [PATCH 0/6] cover glyph support

Behdad Esfahbod <[email protected]>
Newsgroups gmane.comp.lib.cairo
Message-ID <CAF63+7Uabr=62NB21nz4mKSnbc+K_MhEtd1ZGORQ8DBASea7bg@mail.gmail.com>
Thanks Matthias for looking into this.  I reviewed your patches, and while
there's a lot that is left to be done, I agree it's best to merge this and
get it into a release as soon as possible.

Cheers,

behdad

On Fri, Apr 8, 2016 at 8:22 PM, <[email protected]> wrote:

> From: Matthias Clasen <[email protected]>
>
> Its been almost three years since Behdad posted a quick sketch
> of how support for colored glyphs could look in cairo
> (https://github.com/behdad/cairo/commits/color-emoji).
> Over the last few days, I've spent some time on turning this
> into a more complete solution.
>
> The patches in this series provide fully working support for
> colored glyphs in OpenType fonts for the image compositor and
> the xlib compositor, and should be mergable.
>
>
> Matthias Clasen (6):
>   Add support for color glyphs to cairo_scaled_glyph_t
>   Support loading color glyphs with freetype
>   Expose 'has color glyphs' as a scaled font property
>   Implement has_color_glyphs for freetype
>   Add color glyph support to the image compositor
>   Support color glyphs in the xlib compositor
>
>  src/cairo-ft-font.c                |  75 ++++++++++---
>  src/cairo-image-compositor.c       | 220
> +++++++++++++++++++++++++------------
>  src/cairo-scaled-font-private.h    |   3 +
>  src/cairo-scaled-font.c            |  30 +++++
>  src/cairo-xlib-render-compositor.c |  29 +++++
>  src/cairoint.h                     |  11 +-
>  6 files changed, 278 insertions(+), 90 deletions(-)
>
> --
> 2.7.3
>
> --
> cairo mailing list
> [email protected]
> https://lists.cairographics.org/mailman/listinfo/cairo




-- 
behdad
http://behdad.org/

-- 
cairo mailing list
[email protected]
https://lists.cairographics.org/mailman/listinfo/cairo
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.