| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Add some visualizations of gravity.
|
|\
| |
| |
| |
| | |
docs: Add more details
See merge request GNOME/pango!393
|
|/
|
|
|
| |
Add some visualization of alignment and justification
to the PangoLayout docs.
|
|\
| |
| |
| |
| | |
docs: Some clarifications
See merge request GNOME/pango!392
|
| |
| |
| |
| | |
Add a cross-reference to the PangoAlignment docs.
|
|/
|
|
|
| |
Add some more detail around baseline-to-baseline
distances.
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Reimplement pango_layout_move_cursor_visually
Closes #587, #585, and #157
See merge request GNOME/pango!389
|
| |
| |
| |
| |
| | |
Make the docs for pango_layout_move_cursor_visually
a bit more clear.
|
| |
| |
| |
| |
| | |
Test the line end handling of
pango_layout_move_cursor_visually.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Reimplement this function based on pango_layout_get_cursor_pos.
This is a bit less efficient, but it fixes cases where the old
implementation would get stuck.
Fixes: #587, #585, #157
|
| |
| |
| |
| |
| | |
Try to disambiguate run boundaries better.
Not sure this works as intended, yet.
|
| |
| |
| |
| | |
Some of these currently fail.
|
| |
| |
| |
| |
| | |
We need to apply trailing properly, by skipping
characters.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
markup: Allow specifying size in pt or px
Closes #67 and #23
See merge request GNOME/pango!391
|
| |
| |
| |
| |
| |
| |
| | |
Accept values like 200%, in addition to other
ways of specifying sizes in markup.
Fixes: #23
|
| | |
|
|/
|
|
|
|
|
|
| |
Accept values like 12.5pt, in addition to
the other ways of specifying font size in
markup.
Fixes: #67
|
|\
| |
| |
| |
| | |
tests: Avoid bidi in test output
See merge request GNOME/pango!388
|
| |
| |
| |
| | |
Some of these currently fail.
|
|/
|
|
|
|
|
| |
When rendering the text char-by-char, use directional
controls to avoid any bidi reordering.
Update affected tests.
|
|\
| |
| |
| |
| | |
Add an old testcase
See merge request GNOME/pango!386
|
| |
| |
| |
| |
| |
| | |
This checks that we get split cursors in some
cases where we expect it. One of the cases was
broken until the previous commit.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts 681f92d78c2623, after adding the crash
that it alludes to as a test case and verifying that
it no longer crashes.
This commit was causing split cursors to not work
as intended at the end of a mixed-direction string.
Broken since 2008...
|
| |
| |
| |
| |
| |
| |
| |
| | |
This was quite an odyssee:
- Identify commit from 2008 that caused a regression
- Spot the commit message alluding to a crash
- Identify bug number in NEWS for releases from 2008
- Find the bug in the no longer searchable bugzilla.gnome.org
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
itemize: Ignore width in horizontal context
Closes #503
See merge request GNOME/pango!385
|
|/
|
|
|
|
|
|
|
| |
Changes in width only need to break runs in
vertical context.
Update tests and add a new test.
Fixes: #503
|
|\
| |
| |
| |
| | |
gravity: Remove redundant code
See merge request GNOME/pango!384
|
| |
| |
| |
| |
| |
| |
| |
| | |
itemize_state_init was setting gravity-related fields
to their initial values too late, after update_attr_iterator
has already set them to the values for the first run.
Test included.
|
|/
|
|
|
|
| |
Just pass PANGO_GRAVITY_AUTO on to
pango_gravity_get_for_script_and_width.
It has just the same fallback handling.
|
|\
| |
| |
| |
| |
| |
| | |
layout: Add some api for introspection
Closes #476 and #553
See merge request GNOME/pango!373
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add functions to cast PangoAttribute to the various
struct types, so language bindings can get at the
payload.
Fixes: #476
|
|/
|
|
|
|
| |
Add accessors for PangoLayoutLine fields.
Fixes: #553
|
|\
| |
| |
| |
| | |
Start using private vfuncs
See merge request GNOME/pango!383
|
| |
| |
| |
| |
| |
| | |
Add private api to get the necessary information from
the font backend, and drop the hack that was added in
d4356779945855f7cc.
|
| |
| |
| |
| |
| |
| | |
Start using private vfuncs for PangoFont, and use it
to replace the recently introduced pango_fc_font_get_languages
with a frontend api.
|
| |
| |
| |
| | |
We're going to add api.
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
tests: Fix implicit function declaration warnings with gcc
See merge request GNOME/pango!381
|
|/
|
|
| |
This includes stdlib.h for strtol, strtoll and strtod functions declaration
|
|\
| |
| |
| |
| |
| |
| | |
ellipsize: Try harder to find the right font
Closes #575
See merge request GNOME/pango!380
|
|/
|
|
|
|
|
|
|
|
| |
pango_attr_iterator_get_attributes only returns
the innermost attribute of each kind. That is correct
for attributes that supersede each other, but not for
font descriptions, which get merged. So, keep all
font attributes in the returned list.
Update affected tests.
|
|\
| |
| |
| |
| |
| |
| | |
font-desc: Use local double values to store sizes
Closes #580
See merge request GNOME/pango!377
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Under i386 multiplying double and integer values and cast it to integer
may end up to compute the wrong value when only 387 FPU is used, because
the temporary value will be stored in a register whose precision isn't
good enough.
And so, some multiplications which are expected to produce an integer,
will actually return a truncated value, that will be eventually floored.
An example is 1.2 * 12800 that is clearly 15360.0, but will produce
15359 when casted to int in the said i386 environment.
So use a temporary double variable to ensure that we do this computation
in the double scope, before casting to int.
And this will avoid using the said register, even when using more
aggressive optimizations (as per marking the local variable volatile).
Fixes: https://gitlab.gnome.org/GNOME/pango/-/issues/580
|
| |\
| | |
| | |
| | |
| | | |
tests: Avoid a possible invalid access
See merge request GNOME/pango!376
|
| | |
| | |
| | |
| | |
| | |
| | | |
For tests where the wrong fonts break things,
check that we have Cantarell, and skip them
if not.
|
| | |
| | |
| | |
| | |
| | | |
We were rounding things differently, giving
us off-by-one errors on MacOs.
|
| |/
| |
| |
| |
| | |
The return value of setlocale is only good until
the next call. Also, consistently use en_US.UTF-8.
|