| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
We still refer to the project as 'Pango' in docs
and comments, even though the prefix now is 'Pango2'.
|
|
|
|
| |
Sucks that we have to do this manually.
|
|
|
|
|
| |
Add PANGO_HAS_FC/CORE_TEXT/DIRECT_WRITE_FONTMAP macros
to let apps check for the presence of native fontmaps.
|
|
|
|
|
| |
Since we don't have Xft api anymore, the only
usable viewer is the cairo one.
|
|
|
|
|
|
|
|
|
|
| |
We need to be more careful when creating a cairo
font face. Even on Windows or macOS, we may encounter
hb_font_t's that haven't been created from a native
font, so we need to handle those (if we have freetype).
Also simplify the cairo build machinery a bit, and
rely more on cairo-features.h.
|
|
|
|
| |
With separate namespaces, this is no longer necessary.
|
| |
|
| |
|
|
|
|
|
|
| |
Life is easier if the src path matches the installed
header path prefix, so make them match. Update all
users.
|
|
|
|
|
|
| |
Change our versioning setup from "pango 2.0" to "pango2 1.0".
The shared library we install is now libpango2, and the
headers go in /usr/include/pango2-1.0/pango2/.
|
|
|
|
|
|
| |
This makes pango 2 not just parallel-installable
with pango 1.x, but parallel-usable in the same
process.
|
|
|
|
|
|
| |
Sadly, building pixman for ARM64 Windows currently requires clang-cl, so let
people know that they should not let Pango build pixman for them if they are
building for ARM64 Windows.
|
|
|
|
|
| |
Make it more consistent with the other files, since having this file in Windows
CR/LF format is not that important anymore.
|
|
|
|
| |
This makes the text formatting more pleasing to the eye on a web browser.
|
|
|
|
|
|
| |
We had a leftover include in pango-font-family.h.
It is not needed, so drop it and instead include
gio where we use its api.
|
|
|
|
|
| |
If the input is outside the [0, 1] range,
acos returns NaN, so clamp to be safe.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is no more FontConfig support for Windows for Pango2, and let
people know they need DirectWrite support enabled in HarfBuzz and Cairo,
which may not be enabled by default.
Also let people know that if building HarfBuzz as a fallback as a part
of building Pango2, Visual Studio 2017 or later is required to
successfully build HarfBuzz.
Note that HarfBuzz DLLs built with Visual Studio 2017 or later should be
compatible with Pango built with Visual Studio 2015.
|
|
|
|
| |
Most tests don't require cairo apis.
|
|
|
|
| |
This reverts commit 1c3973c9eee4dffb7e853a80f57a3e26dad4b781.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Just so I can make a snapshot release.
|
| |
|
|
|
|
| |
This showed up as wrong slopes with font size > 60.
|
| |
|
|
|
|
| |
Our tests now require G_TEST_SRCDIR to be set.
|
|
|
|
|
|
|
|
| |
Ignore gravity and variations when matching in generic
families, since the hb families contained in there
don't have those fields in their descriptions.
This fixes display of Chinese examples in pango-view.
|
|
|
|
| |
This is enormous fiddling, and should be much simpler.
|
|
|
|
|
|
| |
To use it, call pango-view with
--userfont --font "Userfont 20"
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
There is no way to do anything useful outside
of Pango with these functions, so keep them
private.
|
|
|
|
| |
Move this to PangoHbFont.
|
|
|
|
|
| |
Using %p is not a good idea here, since its output
is platform-dependent. Thankfully, its easily avoided.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sadly, the APIs and COM types in dwrite.h that is shipped with the
Windows SDK at least is C++ only, so we can't just include it in C files
directly. No version of the Windows SDK ship dwrite.h that is
compatible with C, unlike many of the DirectX headers that at least
shipped in the past with C support.
Instead, add a C++ source file that does the work to acquire the
cairo_font_face_t that we need from the DirectWrite IDWriteFontFace that
we added whe we populated the font map, and call that function from
pangocairo-font.c. Make the definition of
create_cairo_font_face_for_hb_font() on DirectWrite builds marked with
static, as with the CoreText and FontConfig builds.
As a consequence, make sure pangocairo-private.h uses C linkage so that
things will link properly when DirectWrite is being used.
|
|
|
|
|
|
|
|
|
| |
Pango is now a single library with all its available backends built in the main
DLL, so we don't need to (nor should) build resource files for PangoWin32, plus
that file has been dropped.
Likewise, also drop the pangocairo.rc.in file template, since that is also no
longer referenced
|
|
|
|
|
|
| |
We need to extract the itemize attributes
first, or we'll miss attributes that are classified
as affecting both itemization and shaping.
|
|
|
|
|
|
| |
It turns out that using user fonts for
embedding is a bit too involved, so lets
keep the shape attribute machinery around.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
In order to build with DirectWrite support, HarfBuzz must also be built
with DirectWrite support, which is disabled by default. Tell the
fallback build to look for DirectWrite and enabled it as a result-it
should be sufficiently present for Visual Studio with the Windows 8.0
SDK, and we are likely using a Windows 10 SDK since we require Visual
Studio 2015 or later for MSVC builds.
Remove the line in .gitlab-ci/test-msys2.sh that requests this support
since we are putting this in the main Meson build files.
|
| |
|
| |
|
|
|
|
|
|
| |
It is what the font chooser expects.
Also, make Sans an alternative to Sans-serif.
|
| |
|
|
|
|
| |
The font chooser seems to rely on this behavior.
|