| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
When multiple fontmaps are created in quick
succession, we would send off a thread to call
FcInit for each one of them, which is not really
necessary. Just do it once.
|
|\
| |
| |
| |
| | |
release: Update included subprojects
See merge request GNOME/pango!304
|
|/
|
|
|
| |
Failure to do so led to a slightly outdated gi-docgen
in the 1.48.4 tarball.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Add an asan option that gives better traces
See merge request GNOME/pango!303
|
|/ |
|
|\
| |
| |
| |
| | |
Add some markup examples
See merge request GNOME/pango!301
|
| |
| |
| |
| | |
A little color doesn't hurt.
|
|\ \
| |/
| |
| |
| |
| |
| | |
Improve letterspacing with marks
Closes #541
See merge request GNOME/pango!298
|
|/
|
|
|
|
|
|
| |
harfbuzz puts marks into their own clusters, so we need
to work a little harder to keep non-spacing marks placed
over their base character.
Fixes: #541
|
|\
| |
| |
| |
| | |
Memdup2
See merge request GNOME/pango!300
|
| |
| |
| |
| |
| | |
The g_memdup() function is replaced by a safer version in newer versions
of GLib.
|
|/
|
|
|
| |
We don't necessarily want to depend on a newer version of GLib, given
that we're not really using g_memdup() in the wrong way.
|
|\
| |
| |
| |
| |
| |
| | |
Fix placement of marks in upright vertical text for fonts without vertical metrics.
Closes #454
See merge request GNOME/pango!297
|
| | |
|
|\ \
| |/
|/|
| |
| | |
context: Cache metrics for the current font
See merge request GNOME/pango!299
|
|/
|
|
|
|
| |
GTK calls pango_context_get_metrics() frequently to
determine character widths and alignments, and does not
expect this to involve expensive layout operations.
|
|\
| |
| |
| |
| | |
release script: Include gi-docgen
See merge request GNOME/pango!296
|
| |
| |
| |
| |
| | |
This lets us say 'you don't need to package this'
about gi-docgen.
|
|\ \
| |/
|/|
| |
| |
| |
| | |
Fix a typo in pango/pangowin32-fontmap.c
Closes #540
See merge request GNOME/pango!294
|
| |
| |
| |
| |
| |
| |
| | |
the `Cursive` default fallback to not load/work on Windows
It should be `comic` and not `commic`.
Signed-off-by: Naveen M K <naveen@syrusdark.website>
|
|\ \
| |/
|/|
| |
| | |
build: Add documentation to the release tarball
See merge request GNOME/pango!295
|
| |
| |
| |
| |
| | |
Rebuilding the project with documentation enabled will also rebuild the
documentation.
|
|\ \
| |/
| |
| |
| | |
build: Install documentation
See merge request GNOME/pango!293
|
|/
|
|
| |
We are building it, but never installing it on the system.
|
| |
|
|
|
|
| |
Small updates for gi-docgen.
|
|\
| |
| |
| |
| | |
build: Don't build HarfBuzz prematurely
See merge request GNOME/pango!291
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For Visual Studio builds, since HarfBuzz is built with CMake until
HarfBuzz 2.6.x yet we only require HarfBuzz 2.0.0 or later, we
aren't able to find pre-2.6.x HarfBuzz using Meson's dependency()
method as the support for CMake config files is not done in Meson.
As a result, we need to make sure that we first manually look for the
HarfBuzz/HarfBuzz-GObject libraries before we attempt to use the
fallback mechanism in Meson, so that we won't rebuild HarfBuzz
unneccesarily.
This rebuild will also cause issues for older compilers that don't
have enough support for C++11 as building Harfbuzz with Meson support
requires a C++11 compiler, which was mandated in HarfBuzz 2.5.0.
|
|\ \
| | |
| | |
| | |
| | | |
Gi docs
See merge request GNOME/pango!281
|
| | |
| | |
| | |
| | | |
Its in main now.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add white-on-transparent and black-on-transparent
variants of this png. For now, make white-on-transparent
the one we use. If somebody wants to make this work in
dark mode, we need to tweak the templates.
|
| | | |
|
| | |
| | |
| | |
| | | |
All these were pointed out by gi-docgen warnings.
|
| | |
| | |
| | |
| | |
| | |
| | | |
These don't have enough meat to warrant turning
them into .md files, so just drop them. They are
no longer used.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Convert link syntax and add summaries.
|
| | |
| | |
| | |
| | | |
Convert link syntax, and summaries.
|
| | |
| | |
| | |
| | | |
Add a few more summaries.
|
| | |
| | |
| | |
| | | |
Add summaries. Most of this really should be private.
|
| | | |
|
| | |
| | |
| | |
| | | |
Add summaries, convert markup, etc.
|
| | |
| | |
| | |
| | | |
Add summaries, convert markup, etc.
|
| | |
| | |
| | |
| | | |
Add summaries, convert markup, etc.
|
| | |
| | |
| | |
| | | |
Add summaries, convert markup, etc.
|
| | |
| | |
| | |
| | | |
Add summaries, convert markup, etc.
|
| | |
| | |
| | |
| | | |
Add summaries, convert markup, etc.
|
| | |
| | |
| | |
| | | |
Add summaries, convert markup, etc.
|