| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Commit message written by Colin Walters <walters@verbum.org>
https://bugzilla.gnome.org/show_bug.cgi?id=667960
|
| |
|
|
|
|
|
| |
Oversight in my fallback fix, this resulted in things being wrongly
destroyed due to unrefs. Oops.
|
|
|
|
| |
This was forgotten in commit aecbe27c1b08f517c0e05f03308d3ac55cef490c
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The fallback failed when a "small caps" font was requested. This commit
improves the fallback support. When the first fallback, trying Sans with
the same style fails, we reset the variant, weight and stretch to
default values and try again. With Sans we should always be able to
adhere to the requested style.
Last but not least, output a sensible error message if all fallbacks
fail instead of simply crashing on a NULL pointer somewhere.
|
|
|
|
|
|
|
|
| |
The documentation says 'This array should be freed with g_free() when
it is no longer needed', which really translates to (transfer
container) in introspection annotation jargon.
https://bugzilla.gnome.org/show_bug.cgi?id=677407
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=677407
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=677407
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=677407
|
|
|
|
|
|
|
|
| |
Change the X fontmap code to look for the aliases file
in $XDG_CONFIG_HOME/pango/pangox.aliases instead of
~/.pangox_aliases
https://bugzilla.gnome.org/show_bug.cgi?id=675400
|
|
|
|
|
|
|
| |
Look for the rcfile in $XDG_CONFIG_HOME/pango/pangorc
instead of ~/.pangorc.
https://bugzilla.gnome.org/show_bug.cgi?id=675400
|
|
|
|
|
| |
Same fallback as already used in CoreText font descriptor to Pango
font descriptor conversion.
|
|
|
|
|
|
|
|
|
|
| |
When run as a system trigger, we really don't want to be consulting
e.g. /root/.pangorc. Also, the OSTree build system can run as
non-root, but we don't in this case want to look at /home/user since
the user may not even exist in the password database inside the
chroot.
https://bugzilla.gnome.org/show_bug.cgi?id=667960
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=672133
|
|
|
|
|
|
|
| |
Setting -I$(top_builddir) before -I$(top_srcdir) causes that
g-ir-scanner picks up boxing definitions generated by glib-mkenums.
https://bugzilla.gnome.org/show_bug.cgi?id=672133
|
|
|
|
|
|
|
| |
Part of Bug 454017 - Make relative paths in pango.modules and pangorc
files work relative to the file
Patch from Anselm Kruis.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Patch written in collaboration with Michael Natterer.
Some CTFontDescriptors apparently do not have a style name or font
family name set. This patch makes the code take such corner cases into
account. The font family problem only appears to occur on Snow Leopard
systems, we try to fall back on the font name (postscript name), if that
fails, we fall back on a default fallback.
In some cases a coverage is also not set. (This seems to happen when we
cannot map a broken font back to a correct font descriptor). In such
cases we simply return an empty PangoCoverage, which will likely cause
the engine to fallback on a different font.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We implement font fallbacks by making use of
CTFontCopyDefaultCascadeList, a public, non-exposed, symbol in the
CoreText library. We might want to handle this differently.
The code now also uses a PangoCoreTextFontsetKey and
PangoCoreTextFontKey, similar to the font config backend. This has also
helped to clean up the code in general.
This patch contains two fixes by Michael Natterer:
1. Fix a bug in pango_core_text_font_key_equal() where the return value
of memcmp() was wrongly interpreted.
2. Cache PangoCoverage in PangoCoreTextFont.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It turns out that getting this value as "Int" is incorrect and resulted
in font traits not being returned in some cases. Without traits, an
italic trait is not set, which caused synthetic oblique fonts to be
created when not necessary.
Also use CTFontSymbolicTraits type in the PangoCoreTextFace structure
and do a stricter bit mask check for certainty.
|
| |
|
|
|
|
|
|
|
|
| |
This is using the newly introduce G_DEPRECATED macros
from GLib. Traditional deprecation guards are still in
place.
https://bugzilla.gnome.org/show_bug.cgi?id=661612
|
|
|
|
|
|
|
|
| |
G_UNICODE_COMBINING_MARK was renamed as G_UNICODE_SPACING_MARK soon after
the GLib 2.29.14 release, so fix that in break.c and pango-ot-info.c.
To support GLib on and before 2.29.14, a convenience definition for
G_UNICODE_SPACING_MARK is defined.
|
|
|
|
|
| |
g_atomic_int_exchange_and_add was deprecated in the GLib gatomic.c rewrite,
for GLib 2.29.6, so use g_atomic_int_add for GLib versions 2.29.5+.
|
|
|
|
|
|
|
|
|
|
|
| |
Update the autotools files for:
-Creation of the full VS 2010 project/filter files for pango, pangocairo
and pangoft2 from the templates during "make dist", so that the source
file list can be made up-to-date with each release-this will simplify
maintenance, as this is what is done for the VS 2008 project files.
-Dist the VS 2010 files (with the templates) and related items
|
| |
|
| |
|
|
|
|
|
|
|
| |
With gcc 4.6.1, I get a build error in pango/ because the C++
parts in harfbuzz have not been compiles with -lPIC. Not sure
if this change is 100% correct, but it makes things build
successfully.
|
|
|
|
|
| |
Backported from HarfBuzz-ng:
http://cgit.freedesktop.org/harfbuzz/commit/?id=cc1a8a938b4c13e76b58825a9e1951c4134e634a
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=656014
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=654689
|
| |
|
|
|
|
|
| |
Fixes a regression from ea702f4 which changed PangoFallbackEngine to be
abstract.
|
|
|
|
|
| |
Commit 02f80c9acdec53f58fef0e12f41363c3c4ea1efe broke the build and was
likely committed untested.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The syntax doesn't include this, and apparently it confuses gtk-doc.
|
|
|
|
| |
This reverts commit 00d2842d8a5ded059fc058d05b2cffcf16186710.
|
|
|
|
|
|
|
| |
Some static analysis tool complained about dead code,
and it is right in this case.
https://bugzilla.gnome.org/show_bug.cgi?id=652616
|
|
|
|
|
|
|
|
|
|
| |
All lines that are too long should be ellipsized when ellipsizing is
enabled. Not just those lines where we thought they'd need to be in
advance. It might turn out that a word is too long so that we cannot
wrap it. In that case we still want to break as soon as possible, but
still ellipsize the line.
https://bugzilla.gnome.org/show_bug.cgi?id=649783
|
| |
|
|
|
|
|
|
|
| |
G_CONST_RETURN is headed for deprecation (as per bug #644611). Stop
using it in Pango.
https://bugzilla.gnome.org/show_bug.cgi?id=652202
|
| |
|
|
|
|
| |
Fix CoreText backend to not use the casefold string as family name.
|
| |
|
|
|
|
|
|
|
| |
The entry of the symbols for commit
4587e5d2231b717dd116253a49badc1ba3aa5db5 in this file was not correct.
Fix that here.
|