| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
| |
We want to include api docs for platform-specific
apis. Avoid getting build failures for introspection
by explictly generating a types file with only
the linux types.
|
|\
| |
| |
| |
| |
| |
| | |
Fix glyph extents
Closes #406
See merge request GNOME/pango!134
|
| |
| |
| |
| |
| | |
We want to make sure that the ink rectangles
we return have positive size.
|
|/
|
|
|
|
|
|
| |
We are getting extents with negative height from harfbuzz,
we have to flip them around. This was causing problems
in lilypond.
Closes: https://gitlab.gnome.org/GNOME/pango/issues/406
|
|\
| |
| |
| |
| |
| |
| | |
Fix vertical offsets
Closes #408
See merge request GNOME/pango!130
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was experimentally determined to fix placement
of diacritics in Arabic text. I am not entirely sure
where the negation crept in, compared to 1.43, which
makes me a little uncomfortable.
Fixes https://gitlab.gnome.org/GNOME/pango/issues/408
|
| |
| |
| |
| |
| | |
It doesn't make sense to use the same function
for both h and v advance.
|
|\ \
| | |
| | |
| | |
| | | |
Make PangoFcFont struct available again
See merge request GNOME/pango!133
|
| |/
| |
| |
| |
| |
| |
| | |
Unfortunately, some applications are poking
directly at PangoFcFont struct fields. Put the
structs back in the public headers for now,
but deprecated.
|
|\ \
| | |
| | |
| | |
| | | |
Drop cairo metrics implementation
See merge request GNOME/pango!132
|
| |/
| |
| |
| | |
We can use the hb-based implementation in pangofc-font.c.
|
|\ \
| |/
|/|
| |
| | |
pango/pangofc-shape.c: Fix build
See merge request GNOME/pango!131
|
|/
|
|
|
| |
The hb_tag_t array was declared as an array of hb_tag_t pointers,
whereas it should have been an array of hb_tag_t's.
|
|\
| |
| |
| |
| | |
Use latest version of metrics naming in pangofc-font
See merge request GNOME/pango!128
|
| | |
|
|\ \
| |/
|/|
| |
| | |
Install PangoFc and PangoOT GObject-Introspection
See merge request GNOME/pango!129
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
If we don't install these, we can't load PangoXft and PangoFT2, which
depend on them:
$ GI_TYPELIB_PATH=${DESTDIR}/usr/lib/x86_64-linux-gnu/girepository-1.0 python3
...
>>> from gi.repository import PangoXft
...
gi.RepositoryError: Typelib file for namespace 'PangoOT', version '1.0' not found
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
|
|
|
|
|
| |
We were crashing when ellipsizing text without
any attributes.
Test included.
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Pass the right attributes when shaping ellipses
Closes #397
See merge request GNOME/pango!127
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now that we are splitting attributes into those that
are relevant for itemization and shaping, we need to
make sure to pass the right ones along when ellipsizing,
or we risk picking a wildly mismatching font for the
ellipsis run, causing things to shift vertically.
Test included.
Closes: https://gitlab.gnome.org/GNOME/pango/issues/397
Thanks to Jorge Luis Martinez Gomez for his help
in tracking this down.
|
|\ \
| | |
| | |
| | |
| | | |
Better filtering by font format
See merge request GNOME/pango!126
|
| | |
| | |
| | |
| | |
| | |
| | | |
We are now producing an FcFontSet that has only
font patterns with supported formats, so we no
longer need to skip NULL fonts.
|
| | |
| | |
| | |
| | |
| | | |
As Behdad pointed out, we were mixing up font
format filtering and coverage trimming.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
Reinstate the return type of pango_fc_font_lock_face()
See merge request GNOME/pango!125
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
We did not remove the freetype dependency from libpango
anyway, so bite the bullet, and keep including freetype
headers.
Changing the return type to gpointer broke C++ users,
where casts from void* are not automatic.
|
|\ \
| |/
|/|
| |
| | |
tests: add missing LineBreakTest.txt
See merge request GNOME/pango!124
|
|/
|
|
|
|
|
|
| |
Without this file one of the tests is always skipped:
/text/break/line: /usr/libexec/installed-tests/pango/LineBreakTest.txt not found. Skipping test.
Taken from the Unicode 12.0.0 release.
|
|
|
|
|
| |
Explain variation syntax and allowed values for
other components of pango_font_description_from_string().
|
|
|
|
| |
Add an illustration of logical and ink rects.
|
|\
| |
| |
| |
| | |
Hyphen control
See merge request GNOME/pango!123
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| | |
fc: Ignore more unsupported font formats
See merge request GNOME/pango!122
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|\
| |
| |
| |
| | |
fc: Don't list fonts with unsupported formats
See merge request GNOME/pango!111
|
| |
| |
| |
| | |
This reverts commit 15d643ea3d8c1af1ec8d4b452a8b3e9246e21928.
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| | |
We don't want to list fonts if we can't handle them.
|
|\ \
| |/
|/|
| |
| | |
Revert "Revert "shape: Simplify font function""
See merge request GNOME/pango!121
|
|/
|
|
| |
This reverts commit 5590b99fb6369cd16110bce2a3e8ac6371c3c487.
|
|\
| |
| |
| |
| | |
Round glyphs option
See merge request GNOME/pango!120
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
This lets us explore the influence of subpixel
positioning in various contexts without relying
on gtk applications.
|
| |
| |
| |
| |
| | |
Take the glyph rounding option from PangoContext
and translate it into a shape flag.
|