summaryrefslogtreecommitdiff
path: root/pango/pangocoretext-private.h
Commit message (Collapse)AuthorAgeFilesLines
* coretext: CleanupMatthias Clasen2021-01-041-2/+0
| | | | Remove the unused face setter and field.
* macos: Implement pango_font_get_faceMatthias Clasen2021-01-041-0/+3
| | | | | | | This was returning NULL for coretext fonts. Good that we have tests for this. Fixes: #524
* Move a function back to public headersMatthias Clasen2019-08-221-3/+0
| | | | pango_core_text_font_get_ctfont is meant to be public.
* Remove now unused platform shaping codeKhaled Hosny2019-07-191-9/+0
|
* OS X: build fixesMatthias Clasen2019-07-181-0/+3
|
* Header cleanupMatthias Clasen2019-07-041-0/+37
| | | | | | | Abolish the PANGO_ENABLE_BACKEND and PANGO_ENABLE_ENGINE defines. All backend-only apis are moved into private headers, all apis that were engine-only are marked as deprecated, since engines are.
* Restore scaling of CoreText fonts.John Ralls2018-05-081-0/+2
| | | | Fixes bug 787867.
* CoreText: Remove absolute size and scaling to screen resolution.John Ralls2017-08-151-1/+1
| | | | | | | | | | | | | 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
* Unmark private symbols as exportedEmmanuele Bassi2017-05-231-1/+0
| | | | | | | | Commit ce097c062ea079bf7888d2b2f1f7b17d34f976b6 was a bit too eager to mark symbols as public, and marked some internal functions as exported. If a symbol has an underscore prefix it generally means it's not meant to be public.
* Decorate the symbols in the headers with version macrosChun-wei Fan2016-06-291-0/+9
| | | | | | | From the last commit, decorate all the symbols with the version macros. Also add the version macros in the docs. https://bugzilla.gnome.org/show_bug.cgi?id=767587
* Deprecate module system, skip it for shaper modulesBehdad Esfahbod2015-04-041-2/+9
| | | | | | | | | | | | | | Now shaper is discovered via (previously unused!) font->find_shaper(). I'm keeping that just to allow clients override shaping. Though, even that I'm not sure we want to keep. Wraps shaper in PangoEngineShape structs to keep PangoAnalysis API intact. Deprecated pango-modules.h and some pango-engine.h. Language modules are not moved yet. Wired up PangoFc, PangoWin32, and PangoCoretext shapers.
* Track changes in FontMaps using a serialAlexander Larsson2012-12-061-0/+1
| | | | | | | | This adds the pango_font_map_get_serial method that lets you see if a fontmap has changes since the last check. It adds implementations to all current fontmaps. https://bugzilla.gnome.org/show_bug.cgi?id=340066
* CoreText backend: implement font fallbacksKristian Rietveld2012-01-281-11/+20
| | | | | | | | | | | | | | | 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.
* Handle oblique fonts; synthesize italic fonts when neededKristian Rietveld2011-04-141-0/+1
| | | | | | 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.
* Start implementation of CoreText backendKristian Rietveld2011-04-141-0/+101
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.
View Lorry Controller Status