| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
GTK needs this information to decide how to
render the glyphs, so provide it.
|
|\
| |
| |
| |
| | |
fonts: Redo the get_face implementation
See merge request GNOME/pango!465
|
| | |
|
|/
|
|
|
| |
Now that we have a private class, we can retire
the misplaced vfunc in the fontmap class.
|
|\
| |
| |
| |
| |
| |
| | |
coretext: Set size on font descriptions
Closes #610
See merge request GNOME/pango!464
|
| |
| |
| |
| |
| |
| | |
We were skipping the test that would have found
the brokenness in the previous fix. Lets see if
we can get the test working on MacOs.
|
|/
|
|
|
|
|
|
| |
Set a size on the font description returned by
pango_font_describe(). Otherwise, scaling it
doesn't work.
Fixes: #610
|
|\
| |
| |
| |
| | |
Cosmetics
See merge request GNOME/pango!463
|
| | |
|
|\ \
| |/
| |
| |
| | |
test-shape: Print out glyph classes
See merge request GNOME/pango!460
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
| |
These are not very reliable for things other than
marks, but even that is useful for debugging cluster
handling.
|
|\
| |
| |
| |
| | |
Try harder to disect clusters
See merge request GNOME/pango!450
|
| | |
|
| | |
|
| |
| |
| |
| | |
If we don't have them, just do the fallback.
|
| |
| |
| |
| |
| |
| | |
This variant of pango_glyph_string_index_to_x takes
log attrs so it does not have to compute them when
it needs them to determine grapheme boundaries.
|
|/
|
|
|
|
|
|
|
|
| |
We need to take into account whether the characters
we are counting are actually cursor positions, else
we are bound to look for more carets than the font
has available, sometimes.
This change would benefit from passing log attrs into
pango_glyph_string_index_to_x.
|
|\
| |
| |
| |
| | |
pango-view: Redo --annotate option
See merge request GNOME/pango!459
|
|/
|
|
|
| |
Parse the argument as a comma-separated list
of names. The old numeric arguments still work.
|
|\
| |
| |
| |
| | |
Add pango_layout_iter_get_run_baseline
See merge request GNOME/pango!458
|
| |
| |
| |
| |
| |
| | |
Use the new run baseline api to correct
the positioning of glyph extents and caret
positions.
|
|/
|
|
| |
This is useful information.
|
|\
| |
| |
| |
| | |
layout: Apply rise to cluster extents
See merge request GNOME/pango!457
|
| |
| |
| |
| |
| |
| | |
We can't currently position them correctly for
shifted runs. But at least we can get it right
for the runs on the baseline.
|
| |
| |
| |
| |
| | |
Don't overwrite caret position numbers with
different numbers.
|
| |
| |
| |
| | |
This has been broken all along. :(
|
|/ |
|
|\
| |
| |
| |
| | |
tests: Use introspection for attributes
See merge request GNOME/pango!456
|
| |
| |
| |
| | |
We want vertical carets to be really vertical.
|
| |
| |
| |
| |
| |
| | |
This really needs some more generic treatment.
Update affected test outputs.
|
|/
|
|
|
|
| |
Now that we have introspection helpers for
attributes, we can use them ourselves to make
this code less brittle.
|
|\
| |
| |
| |
| | |
fcfont: Cosmetics
See merge request GNOME/pango!455
|
| |
| |
| |
| | |
This broke the msvc build.
|
| | |
|
| | |
|
|/
|
|
| |
Remove a few duplicated lines and typos.
|
|\
| |
| |
| |
| | |
pango-view: Split caret positions and slopes
See merge request GNOME/pango!454
|
|/
|
|
| |
Still some bits left!
|
|\
| |
| |
| |
| | |
layout: Allocate a bit less
See merge request GNOME/pango!453
|
|/
|
|
|
| |
Instead of throwing away the log_widths array
for every run, keep it around and grow it as needed.
|
|\
| |
| |
| |
| | |
pango-view: Fix caret visualization
See merge request GNOME/pango!452
|
|/
|
|
| |
I was confusing char and byte offsets here.
|
|\
| |
| |
| |
| | |
Keep offsets for items
See merge request GNOME/pango!451
|
| |
| |
| |
| | |
There is more we can do here, but this is a start.
|
| |
| |
| |
| |
| |
| |
| | |
Print out the items num_chars and char_offset, so we
can check that the char_offset implementation works.
Update affected test outputs.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It is very annoying that gtest will dump its
random seed into the output as soon as one calls
g_test_init(). This pollutes our generated output.
Work around that by deferring the g_test_init()
call until after we've dealt with generating
output.
|