magicloud / cairo-core Goto Github PK

API Changes

* CAIRO_FORMAT_RGB96F, CAIRO_FORMAT_RGBA128F

Dependency Changes

pixman 0.36.0

List of changes in this release:

Adrian Johnson (6):
type1: fallback if the font matrix is not a uniform scale
doc: fix link tags code example
pdf: add missing flush
ps: fix invalid matrix in eps embedding
tag_attributes: Allow decimal points in non decimal point locales
scaled-subsets: always include glyphs maps to character 0

Bryce Harrington (5):
Bump version for 1.17.1
RELEASING: Bugzilla no longer needs updated
clip-boxes: Drop too-early return
Release 1.17.2

Carlos Garcia Campos (1):
ft: Use FT_Done_MM_Var instead of free when available in cairo_ft_apply_variations

Jordan Petridis (1):
CI: Fix Docker image uris

Maarten Lankhorst (4):
cairo-trace: Simplify bigendian case in emit_image.
Add support for RGBA128F and RGB96F formats.
png: Add support for writing new floating point formats as 16 bpc png.
png: Add support for 16 bpc png reading as floating point format

Uli Schlachter (3):
.gitlab-ci.yml: Do a verbose build
Remove all traces of NUM_THREADS
Merge branch 'ft-crash' of gitlab.freedesktop.org:carlosgc/cairo

luz.paz (1):
Misc. typos

suzuki toshiya (1):
[cairo-ft-font.c] conditionalize the changes by 3ec4aa24 on 2018-07-16 for legacy FreeType2 without color font feature

Currently it is there because parseModule cannot enable the syntax while parsing Render.hs. I think getTopPragmas could do the trick.

Some string parameters are clearly stated in document as "encoded in utf8".

Warning: the following files would be used as linker inputs, but linking is not being done: include/cairo-core.h

• stack haddock does not call my preprocessor. Thus the documents do not include correct result.

• Associate comments with AST, then exactPrint to keep haddock comments.

• Need to have a haddock preprocessor to generate haddock comments from Cairo manual on web.