| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Our script properties table was last updated in the
Unicode 5.0 era. Add all the scripts up to Unicode 13.
For the properties, I used the same horizontal direction
as harfbuzz, and left the other properties at their
default values.
|
|
|
|
| |
Harbuzz treats this script as RTL, so we should too.
|
|\
| |
| |
| |
| | |
Add another test for pango_attr_list_change
See merge request GNOME/pango!343
|
|/
|
|
|
| |
This tests that we handle more cases of overlapping
attributes properly.
|
|\
| |
| |
| |
| |
| |
| | |
Link to the CSS font-feature-settings docs for pango_attr_font_features_new
Closes #565
See merge request GNOME/pango!342
|
| | |
|
|/
|
|
| |
Fixes https://gitlab.gnome.org/GNOME/pango/-/issues/565
|
|\
| |
| |
| |
| | |
subprojects: Use GLib main branch
See merge request GNOME/pango!341
|
|/
|
|
|
|
|
|
| |
GLib upstream has renamed its `master` branch to `main`.
See https://gitlab.gnome.org/GNOME/glib/-/issues/2348.
Signed-off-by: Philip Withnall <pwithnall@endlessos.org>
|
|\
| |
| |
| |
| | |
Use harfbuzz from the main branch
See merge request GNOME/pango!340
|
|/
|
|
| |
harfbuzz master got renamed to main.
|
|\
| |
| |
| |
| | |
docs: Link syntax fixes
See merge request GNOME/pango!339
|
|/
|
|
|
| |
Now that gi-docgen warns about link syntax errors,
we can find and fix them.
|
|\
| |
| |
| |
| | |
Explicitly preserve unlimited attributes
See merge request GNOME/pango!338
|
| |
| |
| |
| | |
Test the fix in the previous commit.
|
|/
|
|
|
| |
When calling pango_attr_list_update(), we must not
change the limits or attributes that are unlimited.
|
|\
| |
| |
| |
| | |
docs: Fix link syntax in a few places
See merge request GNOME/pango!337
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Avoid unsigned int pitfalls
Closes #561
See merge request GNOME/pango!336
|
| | |
| | |
| | |
| | | |
This captures bug fixed in the previous commit.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
When we tried to catch attr list overflow in
895759096309e7c, we overlooked that add - remove
can be negative, leading to unexpected results.
Avoid this case.
Fixes: #561
|
|\ \
| |/
|/|
| |
| | |
docs: Add a missing backtick
See merge request GNOME/pango!335
|
| |
| |
| |
| |
| | |
Only build pango-segmentation if we have cairo.
And add --version here too.
|
| | |
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
docs: Reduce redundancy
See merge request GNOME/pango!334
|
|/
|
|
|
|
| |
Remove a boatload of "or %NULL" from nullable parameters
and return values. gi-docgen generates suitable text from
the annotation that we don't need to duplicate.
|
|\
| |
| |
| |
| | |
introspection: Stop using allow-none
See merge request GNOME/pango!333
|
| |
| |
| |
| |
| | |
Remove leftovers like #Type, reduce indentations
to avoid markdown block quotes, etc.
|
|/
|
|
|
| |
The allow-none annotation has been deprecated for a long
time already. Instead use optional and nullable everywhere.
|
| |
|
|\
| |
| |
| |
| | |
fc: Don't use GTask for threading
See merge request GNOME/pango!329
|
|/
|
|
|
|
|
|
|
|
| |
GTask requires a running mainloop, otherwise we
end up leaking task objects and their associated
data. This is not a problem in GTK applications,
but it does show up in batch operation, such as
with lilypond.
To avoid this problem, use plain threads.
|
|\
| |
| |
| |
| | |
test-break: Make help output work again
See merge request GNOME/pango!332
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The commit message for d476d2a944500f8553 said
"word boundaries", but the code checked for line
breaks. That was wrong, since it also made hyphens
disappear at SHY, where we very much want them.
Update affected tests.
|
| |
| |
| |
| |
| |
| |
| | |
test-break has a helpful text that explains
the maining of the output. Unfortunately,
the --help option is taken by g_test_init(),
so make this available with --legend.
|
|\ \
| | |
| | |
| | |
| | | |
break: Fix an inconsistency with sentence breaks
See merge request GNOME/pango!330
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When we retroactively remove a sentence boundary
because of rule SB8, we were not cleaning up the
sencence_start/end markers that have already been
derived from it. This can be seen in urls like
http://www.unicode.org/reports/tr29,
where we don't have any sentence boundaries, but
we leave a stray sentence_start/end at the first
/ after ".org".
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
Add pango-segmentation
See merge request GNOME/pango!331
|
| |/
| |
| |
| | |
A little utility to show text segmentation.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Add some NULL checks
Closes #268
See merge request GNOME/pango!328
|
| |/
| |
| |
| |
| |
| |
| | |
Originally suggested by Philipp Withnall in
https://bugzilla.gnome.org/show_bug.cgi?id=778655
Fixes: #268
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Ensure ellipsized lines have the right width
Closes #24
See merge request GNOME/pango!326
|
| |/
| |
| |
| |
| |
| |
| | |
Otherwise, ellipsized text will 'vibrate', as the
size changes.
Fixes: #24
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Make pango_layout_line_get_height work
Closes #487
See merge request GNOME/pango!327
|
| |/
| |
| |
| |
| |
| |
| | |
We were just never setting the height. Ouch!
Test included.
Fixes: #487
|
|\ \
| | |
| | |
| | |
| | | |
Cosmetics
See merge request GNOME/pango!325
|
| |/ |
|
|\ \
| |/
|/|
| |
| |
| |
| | |
layout: handle empty lines better
Closes #499
See merge request GNOME/pango!324
|