| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
When versions of Meson with bug
https://github.com/mesonbuild/meson/issues/7515 are no longer widespread,
the Pango test suite should diagnose which tests are skipped again.
Versions 0.55.0 to 0.55.2 inclusive have the bug; version 0.55.3 is OK.
This reverts commit 440f9c2609b7f5f9d8f65619b029a5eb660de88b.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|\
| |
| |
| |
| | |
misc fixes
See merge request GNOME/pango!242
|
| |
| |
| |
| | |
This was broken in f6032b754fd76ebbf0ae6.
|
| |
| |
| |
| | |
These were showing up as errors from lsan.
|
|/
|
|
| |
This broke when I recently reshuffled things.
|
|
|
|
|
|
|
| |
meson 0.55 considers tests using it to be FAIL.
I disagree, but lets quietly skip until 0.55.1
is available.
|
|
|
|
|
| |
Create the PangoContext for the test after resetting the locale, and use
the en_US.utf8 name, as it seems to be the name used by Fedora.
|
|
|
|
|
| |
When dumping the diff between the computed and expected results, we need
to respect the TAP format and place "#" in front of each line.
|
|
|
|
|
| |
There's no point in running a tests if we know the locale isn't there.
The reason gets logged, so the developer can decide to install it.
|
|
|
|
|
|
|
|
| |
Do not use homegrown assertion and failure macros, when GTest has
perfectly functional API to deal with all the cases Pango covers.
Using GTest also allows us to rely on appropriate formatting for
results and logging.
|
|
|
|
|
| |
This causes some changes in the output.
Update expected output.
|
|
|
|
|
| |
Share the attribute printing code between
all the tests, update expected output to match.
|
|
|
|
|
| |
We need to use a Unicode locale in order to test
Emoji and similar glyphs.
|
|
|
| |
This reverts commit 3e754defc364a89b2136894399b3463976840156
|
|
|
|
|
|
|
|
|
| |
This commit replaces the PangoScript enum by a
typedef to GUnicodeScript, and preserves the old
enum values as defines.
This depends on adding an enum type for GUnicodeScript
in gobject.
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Don't include unistd.h on Windows, and include io.h if necessary,
as Windows compilers may not ship with it.
https://bugzilla.gnome.org/show_bug.cgi?id=783274
|
|
|
|
|
|
|
| |
coverity says: Using uninitialized value "index2". It didn't
notice that the only time we can reach the index = index2
assignment with index2 still uninitialized is when we are
never going to look at index again.
|
|
|
|
| |
These will be reused later.
|
|
|
|
|
| |
For some reason (that I haven't been able to track down), this
fails in the installed tests on build.gnome.org.
|
|
|
|
|
|
| |
For some reason, the test-layout test does not show the
font size when run on build.gnome.org. Try harder to make
it use the Cantarell 11 font that I want it to use.
|
|
|
|
|
| |
Run diff over the output to give a meaningful error if the
comparison fails.
|
|
This tests works similar to the markup parser tests -
we populate a layout with known data, and then compare
a dump of its properties with expected output.
|