| 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.
|
| |
|
|
|
|
| |
Fixes https://gitlab.gnome.org/GNOME/pango/-/issues/565
|
|
|
|
|
| |
Now that gi-docgen warns about link syntax errors,
we can find and fix them.
|
|
|
|
|
| |
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
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|/ |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\ \
| |/
|/|
| |
| | |
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 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
|
| |/ |
|
|/
|
|
|
|
|
| |
When using line-spacing, we were not giving
empty lines their expected width. Fix that.
Fixes: #499
|
| |
|
|
|
|
|
|
|
| |
pango_layout_set_width was trying to avoid invalidating
lines in some cases, but it failed. Which is good, since
this is incorrect, since it did not take possible
ellipsization into account.
|
|
|
|
|
|
|
|
|
|
| |
We only want to insert hyphens when we are breaking
inside a word.
Update affected tests (hyphen-or-not shows up in the
analysis flags in the output of test-layout).
Fixes: #558
|
| |
|
|
|
|
| |
Fix for memory leaks around PangoWin32Font
|
|
|
|
|
| |
Clarify that the exact style of rendering is up
to the PangoRenderer in use.
|
|
|
|
| |
Mainly for my own education.
|
|
|
|
|
|
| |
GLib now causes compiler warnings when passing a
volatile variable to g_atomic_ apis. Drop the volatile
to pacify gcc.
|
|
|
|
|
|
|
| |
We were erroneously setting fc_initialized back to 1
in one place. But now 1 means 'wait for the FcInit thread
that is already underway. Setting it to 2 restores the
intention.
|
|
|
| |
This reverts merge request !309
|
|\
| |
| |
| |
| | |
Fix deadlocks
See merge request GNOME/pango!310
|
| |
| |
| |
| |
| |
| |
| | |
We were erroneously setting fc_initialized back to 1
in one place. But now 1 means 'wait for the FcInit thread
that is already underway. Setting it to 2 restores the
intention.
|
| |
| |
| |
| |
| |
| |
| | |
Extend the PangoUnderline and PangoOverline enumerations to
cover dashed and dotted variants of the various lines, add
api to PangoRenderer to render such lines, and implement it
in the cairo renderer.
|
| |
| |
| |
| | |
We are going to add new api.
|
| |
| |
| |
| |
| |
| |
| | |
Turns out the case ranges really just gcc extensions,
and do not work with msvc. So, do things the hard way.
Still keeping the early check for ASCII.
|
| | |
|
| |
| |
| |
| | |
Make a bit more use of our types.
|
| |
| |
| |
| | |
No need to walk to the end if we are done.
|
| | |
|
|/
|
|
|
|
| |
Open-code the bsearch here. These functions
show up in profiles, since itemizations uses
an Emoji iter.
|
|
|
|
| |
Just reshuffling existing docs.
|
|
|
|
| |
Some formatting fixes for default_break.
|