| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changes meson.build to match what configure.ac already does. The
code doesn’t have separate conditions for whether fontconfig and
freetype are available: if freetype compilation is enabled, it assumes
that fontconfig is also available.
Previously, systems with freetype available, but no fontconfig, would
fail to compile Pango due to trying to link against non-existent
fontconfig symbols.
Signed-off-by: Philip Withnall <withnall@endlessm.com>
https://bugzilla.gnome.org/show_bug.cgi?id=792363
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=792231
|
|
|
|
|
|
|
|
| |
We call pango_fc_font_key_init on a stack-allocated temporary
lookup key, with the expectation that it does not have to be
freed. In the case where we want to use it as key in the font_hash,
we call copy() on it. So, don't duplicate the variations string
in init() - it will get duplicated in copy() later.
|
| |
|
|
|
|
|
| |
Keep the autotools and meson builds in sync, as far
as requirements are concerned.
|
|
|
|
| |
We've added new API for font variations.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Specify just the axis part in the attribute, so this test
can be used with any font supporting font variations.
|
| |
| |
| |
| |
| |
| |
| | |
We pass them in through FcPattern to the cairo_face already, no need
to pass here again.
Yeah, I know... /tears
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This tests the clamping of axis values, which freetype
is supposed to do. It wasn't working when we tried it.
|
| |
| |
| |
| |
| | |
This uses markup to demonstrate font variations.
It nees the 'Selawik Variations test' font.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This commit lets PangoFontDescription carry font variation
information as a string. Only pangocairo has been updated
to make use of this information. We pass it to harfbuzz
for shaping, and we pass it to cairo when creating scaled
fonts.
|
| |
| |
| |
| |
| |
| | |
Add a quick test for iterating through attribute lists
that piggy-backs on the markup tests - we already have
attribute lists and a place for expected results here.
|
|/
|
|
| |
This adds some tests around the new variations field.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This function is unused since 2004! Last use was dropped in commit
2cdd74591a2b885dbc31292d20dabba81d42faf0. Currently it is just causing
compiler warnings:
[40/111] Compiling C object 'pango/pangoft2-1.0@sha/pangoft2.c.o'.
/usr/include/freetype2/freetype/fterrdef.h: In function ‘_pango_ft2_ft_strerror’:
/usr/include/freetype2/freetype/fterrdef.h:235:17: warning: initializer-string for array of chars is too long
"found FDEF or IDEF opcode in glyf bytecode" )
^
../pango/pangoft2.c:537:38: note: in definition of macro ‘FT_ERRORDEF’
#define FT_ERRORDEF( e, v, s ) { e, s },
^
/usr/include/freetype2/freetype/fterrdef.h:234:3: note: in expansion of macro ‘FT_ERRORDEF_’
FT_ERRORDEF_( DEF_In_Glyf_Bytecode, 0x9C,
^~~~~~~~~~~~
/usr/include/freetype2/freetype/fterrdef.h:235:17: note: (near initialization for ‘ft_errors[75].msg’)
"found FDEF or IDEF opcode in glyf bytecode" )
^
../pango/pangoft2.c:537:38: note: in definition of macro ‘FT_ERRORDEF’
#define FT_ERRORDEF( e, v, s ) { e, s },
^
/usr/include/freetype2/freetype/fterrdef.h:234:3: note: in expansion of macro ‘FT_ERRORDEF_’
FT_ERRORDEF_( DEF_In_Glyf_Bytecode, 0x9C,
^~~~~~~~~~~~
|
|
|
|
|
| |
The gobject-introspection macros are ubiquitous now, so remove the copy in
acinclude.m4.
|
|
|
|
|
|
|
|
| |
Now one can use cairo_set_font_options(), whereas before they had to
use pango_cairo_context_set_font_options(). If the latter is used,
it will override the former.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=790747
|
| |
|
| |
|
|
|
|
|
|
| |
The fixup_broken_linebreaktest variable is not needed any more.
https://bugzilla.gnome.org/show_bug.cgi?id=789625
|
|
|
|
|
|
|
| |
Add char break test cases for the is_char_break variable,
and fixup_broken_linebreaktest is not used any more.
https://bugzilla.gnome.org/show_bug.cgi?id=789625
|
|
|
|
|
|
| |
For most cases, the is_char_break variable should be TRUE.
https://bugzilla.gnome.org/show_bug.cgi?id=789625
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=781857
|
|
|
|
|
|
| |
Support Line Break of Unicode 9.0.
https://bugzilla.gnome.org/show_bug.cgi?id=788115
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The baseline is the baseline of the first line of text in the layout, so
we can simply _get_extents_internal and use the extents of the first
line we get from that.
This is not a perfect solution (e.g. gtk+ calls pango_layout_get_extents
before a pango_layout_get_baseline call and the former calls
get_extents_internal anyway, so we compute the extents twice...) but it
improves the situation pointed out by the comment in
pango_layout_get_baseline.
https://bugzilla.gnome.org/show_bug.cgi?id=788643
|
|
|
|
|
|
|
|
| |
Since PangoLayout caches the amount of lines it contains in
->line_count, we can use this to pre-allocate an Extents array of the
appropriate size.
https://bugzilla.gnome.org/show_bug.cgi?id=788643
|
|
|
|
|
|
|
| |
Use the new _pango_layout_get_iter and _pango_layout_iter_destroy
instead.
https://bugzilla.gnome.org/show_bug.cgi?id=788643
|
|
|
|
|
|
|
| |
And add _pango_layout_get_iter as well as _pango_layout_iter_destroy
that can be used for internal, stack allocated PangoLayoutIters.
https://bugzilla.gnome.org/show_bug.cgi?id=788643
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=788643
|
|
|
|
|
|
|
| |
Use the HIGHENTROPYVA linker option on x64 builds with MSVC 2012 and
later to enhance the security of the built binaries.
Pointed out by Ignacio Casal Quinteiro.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=787194
|
|
|
|
|
|
|
|
|
|
| |
Don't use --include-uninstalled, it's not needed with Meson because we
take care of inter-gir target dependencies.
Add girs and typelibs to the relevant libpango*_dep declared
dependencies so that they can be used via subprojects.
https://bugzilla.gnome.org/show_bug.cgi?id=787414
|
|
|
|
|
|
|
|
| |
Like the autotools builds, build the .rc files for the PangoCairo,
PangoFT2, PangoWin32 and Pango DLLs so that people can see the version
info more easily.
https://bugzilla.gnome.org/show_bug.cgi?id=783274
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=786887
|
|
|
|
|
|
| |
Skip the space characters in sentence start/end.
https://bugzilla.gnome.org/show_bug.cgi?id=785978
|
|
|
|
|
| |
Let people know about the situation where one is able to build the
introspection files directly from within the Visual Studio projects.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the introspection NMake Makefiles buildable from within the
Visual Studio projects, so that the whole Visual Studio build process
would be simplified. At its current state, this will build the
introspection files for PangoCairo and Pango, but does not include
PangoFT2 support, so this is not supported in the [Release|Debug]_FC
configs. For this to work, one needs to have a complete installation of
GObject-introspection in $(GlibEtcInstallRoot), and will need to ensure
that PythonDir (or PythonDirX64 on x64 systems) corresponds to the
same Python series that was used to build GObject-Introspection.
This needs to be built (and cleaned) separately as this is not built by
default, by building/cleaning the pango-introspect project directly.
In this commit, also rename the PythonPath entries in the projects and
property sheets, so that we avoid getting confused with the PYTHONPATH
envvar; and for Visual Studio 201x builds, we use Python 3.4.x by
default 2010, 2012 and 2013, and 3.6.x by default for 2015 and 2017, as
what is done now in GObject-Introspection projects.
|
| |
|
|
|
|
|
|
|
| |
Behdad pointed out that I didn't get it right for
flags and for sequences ending in a skin tone modifier.
Fix that.
|