| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Newer harfbuzz in F37 changes this.
|
|\
| |
| |
| |
| |
| |
| | |
tests/meson.build: install nofonts/fonts.conf as it is required by tests
Closes #713
See merge request GNOME/pango!654
|
| |
| |
| |
| | |
Fixes: https://gitlab.gnome.org/GNOME/pango/-/issues/713
|
|/
|
|
|
|
|
| |
Document the format, and improve the parser a bit,
so we can use this format in GtkBuilder.
Update affected tests.
|
| |
|
|
|
|
|
|
|
| |
Test that the layout is made up entirely of unknown
glyphs if we have no font. The main point of this
test is to ensure that we don't crash if analysis->font
is NULL.
|
| |
|
|
|
|
|
| |
This test is known to fail, and mesons xfail support
is unfortunately broken.
|
|
|
|
|
|
|
|
|
|
| |
With a text of "ර් ", we were accidentally producing
a cursor position outside of the [start_xpos, end_xpos]
range, which clearly makes no sense.
Test included.
Fixes: #684
|
|
|
|
| |
The rounding, it hurts...
|
|
|
|
| |
Rounding differences are our downfall :(
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When moving the cursor off the paragraph end to
the left in RTL text, we were moving to the previous
line, and not to the next line, as expected.
Test included.
Fixes: #679
|
|
|
|
|
|
|
|
|
| |
This was showing up as crashes in pitivi and inkscape.
The added test does not crash, but it does produce
the wrong result without the fix.
Fixes: #678
|
|
|
|
|
|
|
| |
When PangoAttrList was changed to use an array,
we lost the code that maintained non-decreasing
order in pango_attr_list_change. Bring it back,
and add a test for this.
|
|
|
|
|
| |
This tests that our test font configuration
produces the expected font enumerations.
|
|
|
|
|
|
|
| |
We were not actually preferring a monospace
font for the monospace alias.
Update affected tests.
|
|
|
|
|
|
| |
f494181f added this but didn't install it. Related to #648.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
|
|
| |
This reverts commit 053c9ff8ab00d6d7d4b7cbe8aeeaca58c0982df1.
|
|
|
|
|
| |
There are unfortunately some rounding differences,
which I believe are due to harfbuzz changes.
|
|
|
|
|
|
|
|
|
| |
The output from the testboundaries tests just
overwhelms the test reports and makes it hard
to find the actual problems. Stop that.
You can still get the noise, by passing --verbose
to the tests.
|
|
|
|
|
|
|
|
|
| |
handling of segmentation attributes can introduce
line breaks, after we removed them in allow_breaks
handling. Change the order to handle allow_breaks
last, so this doesn't happen.
Update affected tests.
|
|
|
|
|
|
|
|
|
|
|
| |
We were passing a format specifier that starts
with ' ', which some implementations of that API
don't like.
This change removes an extraneous space from the
output. Update affected tests.
Fixes: #659
|
|
|
|
| |
Just use g_object_ref/unref.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
If gap is zero, don't limit the inserted attributes;
that does not make sense. Spell out the different
use cases in the docs.
Testcase included.
Fixes: #653
|
|\
| |
| |
| |
| | |
Add a test for letterspacing
See merge request GNOME/pango!570
|
| |
| |
| |
| |
| | |
This tests that we turn off ligatures when letterspacing
is enabled.
|
|/
|
|
|
| |
Add API to extract the slant ratio from a PangoMatrix.
Tests included.
|
|
|
|
|
| |
Best to compare precise sizes and take rounding
out of the equation.
|
|
|
|
| |
Fixes: #648
|
|
|
|
|
|
|
| |
The Microsoft paper I was citing actually recommends
1/4 em for ASCII space. Make it so...
Update affected tests.
|
|
|
|
|
|
|
|
|
|
| |
Follow the Microsoft Typography recommendations from
https://docs.microsoft.com/en-us/typography/develop/character-design-standards/whitespace
and use half of an em for missing space.
Update affected tests.
Fixes: #647
|
|
|
|
|
| |
This test verifies the fixes for the
situation described in #646.
|
|
|
|
|
|
| |
Oops, we were not serializing the height at all.
Update all affected tests.
|
|
|
|
|
|
|
|
|
|
|
| |
When coming up with a width for a missing space,
we were just measuring the hex digits. But in
subsetted fonts, such as the ones we use for ci,
hex digits might well be missing. Take that into
account and still provide some nonzero width
for space.
Update affected tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is a difficult dance between HarfBuzz and pango
which glyphs we let hb synthesize, and which ones
we need to fake ourselves.
HarfBuzz knows how to create other spaces from 0x20,
so if the font is lacking spaces, we want to tell
HarfBuzz that we don't have that glyph *except* for
0x20 where we need to fake one, and provide HarfBuzz
with a suitable width.
Update affected tests.
|
|
|
|
|
|
|
|
|
| |
This reverts commit ccb651dd2a876a4f4a4cb9351f05332173e709ba.
This broke vertical text rendering, see
https://gitlab.com/inkscape/inkscape/-/issues/2950.
Update affected tests and add a vertical test.
|
|
|
|
|
|
|
|
|
|
|
| |
HarfBuzz knows how to synthesize spaces, we just
need to tickle it in the right way.
Test included.
Update affected tests.
Fixes: #641
|
|
|
|
| |
This tests the fix in the previous commit.
|
| |
|
|
|
|
|
|
|
|
|
| |
We can't break in a tab run.
This fixes an assertion found by afl.
Testcase included.
Fixes: #638
|
|
|
|
|
|
|
|
|
|
| |
We an only use the line_width - remaining_width
shortcut if we are actually maintaining remaining_width,
i.e. not if we don't wrap lines.
Testcase included.
Fixes: #635
|
|
|
|
| |
Update affected test outputs.
|
|
|
|
|
|
|
|
|
|
| |
When we uninsert the current tab run, we need to reset
our tab state to prevent last_tab->glyphs to become a
dangling pointer.
Test included.
Fixes: #634
|
|
|
|
|
| |
This will make the font serialization useful
in GTK, where we serialize fonts in node files.
|
| |
|
| |
|
|
|
|
|
| |
Don't calculate line width the hard way when
we can do it much easier.
|
| |
|