| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
This reverts commit c5d86c368128bb9a0be913829da79649fb81f486.
Closes #409
|
|
|
|
| |
We can use the hb-based implementation in pangofc-font.c.
|
| |
|
|
|
|
|
| |
create_base_metrics is not meant to fill in widths.
That is done in _pango_cairo_font_get_metrics.
|
| |
|
| |
|
|
|
|
| |
Fixes bug 787867.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cairo's CGFont backend already handles scaling fonts to the display
resolution, so scaling to the screen screen resolution in Pango's
CoreText backend generates double-sized text on a Retina display.
The layout test depended on providing a (bogus) resolution of 96DPI and
scaling the font to it in order to obtain the "expected" layout
results. This is replaced by adjusting the font size in test-layout.c
if Pango is compiled for CoreText.
https://bugzilla.gnome.org/show_bug.cgi?id=782393
|
|
|
|
|
|
|
|
| |
This partially reverts 25ad29b488d3e2ae10e4fee25602409fa39207f1
which itself was a revert. Apparently we want the change in
CoreText, but not on Win32...
See mailing list discussion.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit b359bb484bc7d27a835cfd6d9ffcaed582ebf2ae.
Bug 694918 - Pango layout is rendered in wrong size if we have
non-identity cairo transformation matrix
I was wrong blindly copying this logic from pangocairo-fc into
pangocairo-win32 and pangocairo-quartz.
The reason we need the it in pangofc is because the fontsize we
get back from fontconfig is multiplied by the ctm scale factor,
so we undo it when loading the font. The same is NOT true about
the non-fc backends, so the copying was totally wrong.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We implement font fallbacks by making use of
CTFontCopyDefaultCascadeList, a public, non-exposed, symbol in the
CoreText library. We might want to handle this differently.
The code now also uses a PangoCoreTextFontsetKey and
PangoCoreTextFontKey, similar to the font config backend. This has also
helped to clean up the code in general.
This patch contains two fixes by Michael Natterer:
1. Fix a bug in pango_core_text_font_key_equal() where the return value
of memcmp() was wrongly interpreted.
2. Cache PangoCoverage in PangoCoreTextFont.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Deduce from the given style name whether a font is oblique. If a font
family does not have an italic or oblique variant, then add synthetic
italic variants that are handled by Pango.
|
|
On Mac OS X systems where CoreText is available (that is, 10.5 or
higher), we will build the CoreText backend instead of the ATSUI
backend. In this case, the ATSUI backend will not be built and
installed. This change is necessary because since Mac OS 10.5
ATSUI has been marked as deprecated.
For older systems, we will have to continue to use the
ATSUI backend.
|