| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
These are just wrappers of g_object_ref/unref.
|
|
|
|
| |
Just use g_object_ref/unref.
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Clarify pango_attr_list_splice docs
Closes #653
See merge request GNOME/pango!574
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If gap is zero, don't limit the inserted attributes;
that does not make sense. Spell out the different
use cases in the docs.
Testcase included.
Fixes: #653
|
| |
| |
| |
| |
| | |
Make it explicit that the spliced-in attributes
are limited to the the 'gap'.
|
|/ |
|
|
|
|
| |
Fixes: #650
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If char is unsigned, the first byte of a non-trivial UTF-8 sequence will
be 0x80 or higher, instead of being negative. In this case we need to
process it as UTF-8, instead of printing only the first byte and then
skipping to the next UTF-8 character.
char is usually signed on x86 and some other architectures, but not on
the ARM or PowerPC families, among others.
Resolves: https://gitlab.gnome.org/GNOME/pango/-/issues/652
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
|
|
|
|
|
|
| |
When the font matrix has uneven scales, we need
to factor that into the slope that we get from
the font metrics.
Tested with a condensed italic Cantarell.
|
|\
| |
| |
| |
| | |
Add a test for letterspacing
See merge request GNOME/pango!570
|
| |
| |
| |
| | |
Just for completeness.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When our font matrix includes a slant, pass that information
to HarfBuzz, so it can adjust its mark positioning, metrics
like caret slope, etc.
This commit corrects the code that pulls the font matrix out
of fontconfig to properly take the flipped y axis between fontconfig
and pango into account.
Requires new api in HarfBuzz > 3.2
|
|/
|
|
|
| |
Add API to extract the slant ratio from a PangoMatrix.
Tests included.
|
|
|
|
|
| |
Face names are not actually guaranteed to be unique,
so don't say that.
|
|
|
|
| |
Mention GListModel.
|
| |
|
|
|
|
|
| |
Always fall back to the base font if the fontset
has no coverage.
|
|
|
|
|
|
|
|
| |
We want to define pango_trace_mark to nothing.
This reveals that we've never compiled these
calls out before, and there are some warnings
to be fixed in that case.
|
| |
|
|
|
|
| |
This will be used in the future
|
|
|
|
| |
This was just an empty header.
|
|
|
|
|
|
| |
This functionality is basically unused.
Lets not keep an array of coverages around
for it.
|
|
|
|
| |
Put PangoFontsetSimple into its own files.
|
|
|
|
|
|
|
| |
The Microsoft paper I was citing actually recommends
1/4 em for ASCII space. Make it so...
Update affected tests.
|
|
|
|
|
|
|
|
|
|
| |
Follow the Microsoft Typography recommendations from
https://docs.microsoft.com/en-us/typography/develop/character-design-standards/whitespace
and use half of an em for missing space.
Update affected tests.
Fixes: #647
|
|
|
|
| |
No surprises here.
|
|
|
|
|
|
|
|
| |
Add a private vfunc to get the (absolute) size
of a font. This default implementation just
pulls it out of the font description, but we
can do implement this cheaper without copying
the font description.
|
|
|
|
|
| |
Rename some variables, so we actually know
what these matrices are.
|
|
|
|
|
|
|
|
| |
When we change font scale for emulating small caps,
keep the original font around in the analysis, and use
it for calculating the run height.
Fixes: #622
|
|
|
|
|
|
| |
Add some api to let us store another font in
a PangoAnalysis. This will be used in the following
commits.
|
|
|
|
|
|
|
| |
We want to avoid trading chars for hyphens
in the margin beyond the set width.
Fixes: #646
|
|
|
|
|
| |
We don't collapse space at the very end, so we should
count such spaces towards the line width.
|
|
|
|
|
|
| |
Oops, we were not serializing the height at all.
Update all affected tests.
|
|
|
|
| |
Add doc comments for some private API.
|
|
|
|
|
|
| |
Stop using fcfont->matrix. This is just a redundant
copy of the matrix that is already available in
the font key. Just use that.
|
|
|
|
|
|
|
|
|
|
|
| |
When coming up with a width for a missing space,
we were just measuring the hex digits. But in
subsetted fonts, such as the ones we use for ci,
hex digits might well be missing. Take that into
account and still provide some nonzero width
for space.
Update affected tests.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is a difficult dance between HarfBuzz and pango
which glyphs we let hb synthesize, and which ones
we need to fake ourselves.
HarfBuzz knows how to create other spaces from 0x20,
so if the font is lacking spaces, we want to tell
HarfBuzz that we don't have that glyph *except* for
0x20 where we need to fake one, and provide HarfBuzz
with a suitable width.
Update affected tests.
|
|
|
|
|
|
|
|
|
| |
This reverts commit ccb651dd2a876a4f4a4cb9351f05332173e709ba.
This broke vertical text rendering, see
https://gitlab.com/inkscape/inkscape/-/issues/2950.
Update affected tests and add a vertical test.
|
|\
| |
| |
| |
| |
| |
| | |
Fix handling of space-less fonts
Closes #641
See merge request GNOME/pango!552
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
HarfBuzz knows how to synthesize spaces, we just
need to tickle it in the right way.
Test included.
Update affected tests.
Fixes: #641
|
|\ \
| |/
| |
| |
| |
| |
| | |
Fix Arabic format chars
Closes #642
See merge request GNOME/pango!553
|
| |
| |
| |
| |
| |
| |
| | |
We can't treat these like spaces, since they are visible
and need the proper font.
Fixes: #642
|
|/
|
|
|
|
| |
This was breaking the build on some macOs versions.
Fixes: #640
|
|
|
|
| |
Fixes: #637
|
|
|
|
| |
It is needed for strtol()/strtoul().
|
|
|
|
|
| |
Add more links to GLib apis and to various
Unicode specs.
|
| |
|