| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes bug 787867.
|
|
|
|
|
| |
Visual Studio does not ship with a unistd.h, so include the proper
header on Windows when unistd.h is not found on Windows.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is possible that we can have the following situations, at least on
Windows:
-FreeType present, FontConfig missing
-Cairo-FT present, with no FontConfig support.
As gen-script-for-lang requires FontConfig, and PangoFT2 depends on
HarfBuzz, FontConfig and Freetype, we need to check for them before we
build PangoFT2, and so that we could include PangoFT2 support in
PangoCairo.
The tests and pango-view have an optional dependency on PangoFT2, so we
need to also check whether we built PangoFT2 before we try to build
things related to PangoFT2.
For the tools, since gen-script-for-lang.c depends on FontConfig, check
for it as well before we build it.
https://bugzilla.gnome.org/show_bug.cgi?id=783274
|
| |
|
|
|
|
|
|
| |
Add a quick test for iterating through attribute lists
that piggy-backs on the markup tests - we already have
attribute lists and a place for expected results here.
|
|
|
|
| |
This adds some tests around the new variations field.
|
| |
|
|
|
|
|
|
| |
The fixup_broken_linebreaktest variable is not needed any more.
https://bugzilla.gnome.org/show_bug.cgi?id=789625
|
|
|
|
|
|
|
| |
Add char break test cases for the is_char_break variable,
and fixup_broken_linebreaktest is not used any more.
https://bugzilla.gnome.org/show_bug.cgi?id=789625
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=788643
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=786379
|
|
|
|
|
|
|
|
|
|
| |
ZWJ is treated as its own class in TR29, and us lumping
them together and then manually checking wc == 0x200d in
various places was causing us to inadvertedly inserting
grapheme breaks in the middle of Emoji ZWJ sequences
where they are not suppose to be.
Add test cases to verify this.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
We're disting only a subset of files with Autotools, but Meson expects
everything we have in Git.
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=782813
|
|
|
|
| |
These are the same testcases from the previous commit.
|
|
|
|
|
|
|
| |
This reverts commit 77b56b4248816c5331ba344f19c45865c8bf2a32.
This file is a copy of a file in the ucd, we should not change
it. Lets add a new test instead.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=780669
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Meson is a meta build system that is:
- fast
- simpler to understand and use
- portable to multiple platforms through different backends
- well integrated with the GNOME platform
- well maintained
Using Meson allows us to build Pango much more quickly, and on all the
platforms we currently target, without any loss of functionality,
compared to Autotools.
Some timing comparisons with hot ccache for both build systems:
* autogen.sh: * meson
real 0m11.149s real 0m2.525s
user 0m8.153s user 0m1.609s
sys 0m2.363s sys 0m1.206s
* make -j$(($(nproc) + 2)) * ninja
real 0m9.186s real 0m3.387s
user 0m16.295s user 0m6.887s
sys 0m5.337s sys 0m1.318s
--------------------------------------------------------------
* autotools * meson + ninja
real 0m27.669s real 0m5.772s
user 0m45.622s user 0m8.465s
sys 0m10.698s sys 0m2.357s
System: Intel Core i7-7500U, SSD, 16GB of RAM
|
|
|
|
|
|
| |
While `.C` is a valid GCC extension for C++ files, it only works for
case sensitive file systems. Let's use `.cpp`, like the rest of the
planet does.
|
|
|
|
|
|
|
| |
g_assert gets neutered by --enable-debug=no, which is not what
we want in tests. Use g_assert_true instead.
https://bugzilla.gnome.org/show_bug.cgi?id=755126
|
|
|
|
| |
GLib enforces this now.
|
|
|
|
|
| |
Exposes an assertion failure:
https://bugzilla.gnome.org/show_bug.cgi?id=541608
|
| |
|
|
|
|
|
| |
Apparently libthai is not threadsafe. This crashes
right away if libthai is enabled...
|
| |
|
| |
|
|
|
|
| |
Fails right now. Fix coming.
|
| |
|
|
|
|
|
|
|
| |
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 tests exercise PangoAttribute, PangoAttrList and
PangoAttrIterator apis.
|
|
|
|
| |
These will be reused later.
|
|
|
|
|
| |
Update the expected output of the layout tests to the previous
change.
|
|
|
|
|
| |
For some reason (that I haven't been able to track down), this
fails in the installed tests on build.gnome.org.
|
|
|
|
| |
This just a small beginning, much more is needed here.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
We see the 'ellipsized' analysis flag in the output now,
as we should.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
This test is modeled after the GMarkup parser tests in GLib.
Test file with a name ending in .markup can be dumped in
tests/markups/, and tests/markup-parse can be used to generate
the expected output files which should be in the same location
and with the extension .markup replaced by .expected.
The test is also used as an installed test.
|
|
|
|
|
|
| |
Follow the prevailing practice and put the installed tests
into $libdir/installed-tests/$PACKAGE instead of
$pkglibdir/installed-tests.
|
| |
|
|
|
|
|
|
| |
If new test api is not available, do without it. In this
case, the tests won't work installed, but they should still
work uninstalled and in distcheck.
|