summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * Try again to debug win32 ci segfaultsMatthias Clasen2019-08-042-1/+6
| |
| * tests: Cover new attribute typesMatthias Clasen2019-08-041-0/+3
| |
| * Add an insert-hyphens attributeMatthias Clasen2019-08-046-2/+86
|/ | | | | | | | | Add a text attribute that allows to suppress insertion of hyphens at intra-word line breaks. This is useful for non-paragraph-like contexts, where line breaks are needed, but hyphens are not expected.
* Merge branch 'ignore-more-unsupported-fonts' into 'master'Matthias Clasen2019-08-041-4/+17
|\ | | | | | | | | fc: Ignore more unsupported font formats See merge request GNOME/pango!122
| * fc: Ignore more unsupported font formatsKhaled Hosny2019-08-041-4/+17
|/ | | | | | | | | | | | | FontConfig uses FreeType’s FT_Get_X11_Font_Format() to get the font format. From the list of font formats it supports, only “TrueType” and “CFF” are supported by HarfBuzz. We now check explicitly for supported formats and reject anything else: https://git.savannah.gnu.org/cgit/freetype/freetype2.git/tree/include/freetype/internal/services/svfntfmt.h#n36 FreeType, however, seems to use “CFF” for both OpenType fonts with CFF table (.otf) and bare CFF fonts (.cff), but the later are not supported by HarfBuzz although they rather rare (outside of PDF files, which shouldn’t be rendered with Pango), so it should be OK.
* 1.44.31.44.3Matthias Clasen2019-08-032-1/+7
|
* Merge branch 'unsupported-formats' into 'master'Matthias Clasen2019-08-042-16/+55
|\ | | | | | | | | fc: Don't list fonts with unsupported formats See merge request GNOME/pango!111
| * Revert "Try to debug win32 ci"Matthias Clasen2019-08-031-1/+1
| | | | | | | | This reverts commit 15d643ea3d8c1af1ec8d4b452a8b3e9246e21928.
| * fc: Don't return fonts with unsupported formatsMatthias Clasen2019-08-031-15/+49
| | | | | | | | | | | | | | | | Make pango_fontset_foreach skip fonts that in formats that harfbuzz doesn't support. Some reshuffling was necessary since previously the code was assuming that the first NULL indicates the end of available fonts.
| * fc: Don't list fonts with unsupported formatsMatthias Clasen2019-08-031-0/+5
| | | | | | | | We don't want to list fonts if we can't handle them.
* | Merge branch 'font-funcs' into 'master'Matthias Clasen2019-08-031-74/+0
|\ \ | |/ |/| | | | | Revert "Revert "shape: Simplify font function"" See merge request GNOME/pango!121
| * Revert "Revert "shape: Simplify font function""Khaled Hosny2019-08-031-74/+0
|/ | | | This reverts commit 5590b99fb6369cd16110bce2a3e8ac6371c3c487.
* Merge branch 'round-glyphs-option' into 'master'Matthias Clasen2019-08-0311-37/+185
|\ | | | | | | | | Round glyphs option See merge request GNOME/pango!120
| * Fix the harfbuzz test for win32Matthias Clasen2019-08-031-1/+4
| |
| * Try to debug win32 ciMatthias Clasen2019-08-031-1/+1
| |
| * pango-view: Add a --subpixel-positions optionMatthias Clasen2019-08-033-0/+8
| | | | | | | | | | | | This lets us explore the influence of subpixel positioning in various contexts without relying on gtk applications.
| * layout: Use the new glyph rounding optionMatthias Clasen2019-08-031-3/+9
| | | | | | | | | | Take the glyph rounding option from PangoContext and translate it into a shape flag.
| * context: Add an option for rounding glyph positionsMatthias Clasen2019-08-033-0/+55
| | | | | | | | | | | | | | | | | | | | | | This is a global option, similar in spirit to font options, so it makes sense to keep it in PangoContext. Default to rounding glyph positions, which preserves the pre-1.44 behavior and should help cure all the 'broken' font rendering with older cairo versions.
| * Add a pango_shape variant that takes flagsMatthias Clasen2019-08-033-32/+108
|/ | | | | The only flag currently defined affects whether glyph positions are rounded or not.
* Remove a unnecessary harfbuzz version checkMatthias Clasen2019-08-031-2/+0
| | | | We require harfbuzz 2.0.0 now.
* build: Install pango-ot headersEmmanuele Bassi2019-08-031-1/+1
| | | | | The refactoring of commit 1bdadfe1aae158fb406e10f81f3ae0533dea1602 missed out an installed header.
* 1.44.21.44.2Matthias Clasen2019-08-022-1/+13
|
* Try to fix win ciMatthias Clasen2019-08-021-1/+1
|
* Make line-spacing opt-inMatthias Clasen2019-08-021-2/+2
| | | | | | | | | Default the new line-spacing property to 0, so spacing continues to work. Applications can opt in to the new line-spacing behavior by setting a non-zero value. This should make spacing in the Gimp work again.
* Merge branch 'more-introspection-fixes' into 'master'Matthias Clasen2019-08-025-20/+64
|\ | | | | | | | | Some more introspection fixes See merge request GNOME/pango!118
| * Add missing transfer annotationsEmmanuele Bassi2019-08-024-7/+7
| |
| * Parse all pangoft sourcesEmmanuele Bassi2019-08-021-4/+3
| | | | | | | | | | | | The PangoFT2 sources have gtk-doc stanzas, so we need to parse them all to avoid warnings from the introspection scanner only having the headers to go by.
| * Decouple PangoOT and PangoFc from PangoFT2Emmanuele Bassi2019-08-021-13/+58
|/ | | | | | | | | | | | | | | | | The PangoFT2 introspection namespace contains symbols from two other namespaces on top of its own PangoFT2 symbols: - PangoOT, the deprecated wrapper for FreeType's OpenType API - PangoFc, the wrapper for FontConfig's API We can only have one namespace per GIR/typelib, so we need to decouple the GIR and typelib introspection data from PangoFT2 into three separate namespaces. These are just new introspection namespaces mapping to their corresponding C symbols; there are no new shared libraries: if you're using PangoFc and PangOT API then you must be linking against libpangoft2 anyway.
* Give upMatthias Clasen2019-08-021-5/+6
| | | | | Somebody on win32 will have to fix this to build without warnings.
* Another attemptMatthias Clasen2019-08-021-1/+3
|
* Last attemptMatthias Clasen2019-08-021-1/+1
|
* Another warning fixMatthias Clasen2019-08-021-4/+1
|
* Merge branch 'introspection-fixes' into 'master'Matthias Clasen2019-08-0212-22/+52
|\ | | | | | | | | Various introspection fixes See merge request GNOME/pango!117
| * Skip Harfbuzz type getterEmmanuele Bassi2019-08-021-1/+1
| | | | | | | | | | Since Harfbuzz does not generate introspection data, we cannot use it for our introspected ABI.
| * Skip some deprecated symbolsEmmanuele Bassi2019-08-021-7/+7
| | | | | | | | | | These symbols are generating warnings because of missing type information, but since they are deprecated we can just skip them.
| * Add a boxed type for PangoAttrIteratorEmmanuele Bassi2019-08-022-0/+8
| | | | | | | | | | | | | | | | Makes it usable by language bindings, and avoids warnings when generating introspection data. We already have the necessary public API, we're just missing a GType for it.
| * Add a boxed type for PangoScriptIterEmmanuele Bassi2019-08-022-1/+17
| | | | | | | | | | Makes it usable by language bindings, and avoids a warning when introspecting the source code.
| * Add PangoCoverage GType getter to the public headerEmmanuele Bassi2019-08-023-8/+7
| | | | | | | | | | | | The `pango_coverage_get_type()` symbol is already public, but declared in a private header. Unless we move it to a public header the introspection scanner can't know that the C type maps to a GType.
| * Ensure arguments name match the documentationEmmanuele Bassi2019-08-023-5/+5
| | | | | | | | Otherwise the introspection scanner will be majorly confused.
| * Ignore unprefixed symbolsEmmanuele Bassi2019-08-021-0/+7
| | | | | | | | | | | | The unprefixed `script_*` symbols are marked as `skip`, but the introspection scanner will still warn about them because the annotations are resolved after parsing the C code.
* | One more warning fixMatthias Clasen2019-08-021-3/+6
| |
* | examples: Avoid deprecated apiMatthias Clasen2019-08-021-2/+1
|/
* Fix a C99 strftime incantationMatthias Clasen2019-08-011-1/+1
| | | | | This is problematic when building pango as subproject of gtk on the win32 ci.
* Merge branch 'compiler-warnings' into 'master'Matthias Clasen2019-08-025-4/+79
|\ | | | | | | | | Compiler warnings See merge request GNOME/pango!116
| * Revert "shape: Simplify font function"Matthias Clasen2019-08-011-0/+74
| | | | | | | | | | | | This reverts commit 315e3d4f6182e4cefde3538ede222e53c000f3e8. This made pango-view segfault in win32 ci.
| * Add a few more warning flagsMatthias Clasen2019-08-011-0/+2
| | | | | | | | | | | | Add warning flags for the just fixed warnings to the build. This is in order to ensure that pango builds in ci as a subproject of gtk.
| * Avoid another compiler warningMatthias Clasen2019-08-011-4/+1
| | | | | | | | Unused-but-set-variable.
| * Avoid an implicit fallthroughMatthias Clasen2019-08-011-0/+1
| | | | | | | | This was pretty clearly unintentional.
| * Annotate implicit fallthroughMatthias Clasen2019-08-011-0/+1
|/ | | | This triggers compiler warnings.
* Merge branch 'simplify-font-funcs' into 'master'Matthias Clasen2019-08-011-75/+1
|\ | | | | | | | | shape: Simplify font function See merge request GNOME/pango!115
View Lorry Controller Status