| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
We were not passing the correct split_offset to
pango_item_split().
Testcase included.
Fixes: #627
|
| |
|
|
|
|
| |
This keeps spiraling :(
|
|
|
|
|
|
| |
If the break is at the end of the item, we
were forgetting to check for the space before
the break.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we are breaking after a space, we must not
count the width of the space towards the line,
since we are zeroing it later.
It is a bit annoying that there are multiple places
where this has to be taken into account.
Another missing bit in this code is that we are
only looking at a single whitespace character before
the break, when we should really look for a sequence
of spaces.
|
|
|
|
|
| |
When unsplitting an item, we were sometimes
calculating the remaining_width incorrectly.
|
|
|
|
| |
We can use the log_widths that we already have.
|
|
|
|
|
|
| |
We only want this inside process_item, so we can
make this a purely local thing, without modifying
log_attrs.
|
| |
|
|\
| |
| |
| |
| | |
coretext: correctly clamp the core text weights at min/max values
See merge request GNOME/pango!502
|
| |
| |
| |
| | |
Addresses bug found in #624
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Our accounting for run lengths is imperfect (mainly
due to log widths for clusters being evenly distributed),
so it can happen that after reshaping the split item,
we find that it does not actually fit in the remaining
width. Previously, we would just use the split run
at that point and produce an overlong line. Instead,
undo the split, disable the breakpoint we used, and
try again.
|
| |
| |
| |
| |
| |
| | |
This undoes the effect of pango_item_split.
We will use this in future commits.
Private for now.
|
| |
| |
| |
| | |
This will let us use some of them during layout.
|
| | |
|
|/
|
|
|
| |
In some cases, we were forgetting to account
for the width of a hyphen.
|
|\
| |
| |
| |
| | |
Bump fontconfig dep to 2.13.0
See merge request GNOME/pango!499
|
| |
| |
| |
| | |
We are requiring a new enough fontconfig now.
|
|/
|
|
|
| |
This is useful information for Harfbuzz to have,
so pass it along.
|
|
|
|
| |
Add the new variant values to the docs.
|
|
|
|
|
|
| |
Take text transforms into account when emulating
Small Caps. This requires us to have log attrs
to determine word starts.
|
|
|
|
|
|
|
|
|
|
|
| |
Split the post-processing off into a separate function
that can take log attrs in addition. This will allow
us to handle word starts when dealing with text transforms
for emulated Small Caps.
So far, this is all private API that is used from PangoLayout.
Please file an issue if you want to access Small Caps emulation
without PangoLayout.
|
|
|
|
| |
Move private API out of the 'Public API' section.
|
|
|
|
| |
pango_itemize_with_font belongs into pango-item-private.h.
|
|
|
|
| |
We want last-one-wins semantics here.
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we detect that one of the other casing variants
is requested, but not available via OpenType font
features, emulate it by splitting the item into
lowercase and uppercase runs and apply a suitable
font scale and text transform to the runs to get
the desired effect.
Still to do: resolve conflics with preexisting
text transform attributes.
|
|
|
|
|
|
| |
Pass all the PangoVariant values through the
FcPattern by translating them into suitable
OpenType features in the pattern.
|
|
|
|
|
| |
Add values for all the css casing variants to
the PangoVariant enum.
|
|
|
|
|
|
|
|
|
|
|
| |
When we detect that Small Caps are requested, but not
available via OpenType font features, emulate Small Caps
by splitting the item into lowercase and uppercase runs
and add text transform and font scale attributes to the
lowercase runs to get the effect of Small Caps.
Still to do: resolve conflicts with preexisting text
transform attributes.
|
|
|
|
|
|
| |
Factor out the 'consider as space' part from the
itemization code, so we can reuse it when breaking
items into upper- and lowercase runs.
|
|
|
|
| |
This is not used by anything yet.
|
|
|
|
|
| |
This will be used in the implementation of emulated
Small Caps.
|
| |
|
|
|
|
|
|
| |
Add a helper function that used to live with the Harfbuzz
shaping code in shape.c. It will be used in the itemize code
too, in the future.
|
|
|
|
|
|
|
| |
Arrange for PANGO_VARIANT_SMALL_CAPS to be translated
into the OpenType feature smcp=1 and back. This makes
small caps survive a roundtrip from font description
to font and back.
|
|
|
|
|
|
|
|
|
|
| |
The hb_font_t we were passing to Harfbuzz
for shaping was not taking context transforms
into account, and therefore was not scaling
advance widths as necessary. Always go through
pangos glyph extents to fix this.
Fixes: #620
|
|
|
|
|
|
| |
Add some more directional formatting characters
to the list of default-ignorables that we make
visible when requested: ALM, LRI, RLI, FSI, PDI.
|
|
|
|
|
| |
pango_fontset_simple_append consumes the font
that it is given.
|
|
|
|
|
| |
For east and west gravity, the logical glyph extents
were still misaligned with the ink extents.
|
|\
| |
| |
| |
| | |
cairo: Produce meaningful logical glyph extents
See merge request GNOME/pango!490
|
| |
| |
| |
| |
| |
| | |
cf_priv->scaled_font is initialized on demand, it may
be NULL. So better call the getter. This was showing
up as failure in the asan test in ci.
|
| |
| |
| |
| |
| | |
Without this, we end up with differences in
metrics of empty runs.
|
| |
| |
| |
| |
| |
| |
| | |
We were looking at the wrong font options here,
causing metrics to not be hinted when they should
be. This was causing some of the empty line height
tests to fail.
|
| |
| |
| |
| |
| | |
Depending on gravity, our logical glyph extents
were empty and mis-aligned. Fix that.
|
|/
|
|
| |
Also drops the null-terminated doc comment as gi-docgen shows that already
if the function is annotated properly
|
|
|
|
|
| |
Add some missing details about new enumerations
and run baselines.
|
|
|
|
| |
from a manual override in gtk-rs
|
| |
|
|
|
|
|
|
| |
This broke glyph extents with gravity north or west.
This reverts commit 20ec670e124e4461075a2967faa29603d25106cc.
|
| |
|