kyamagu / fontconfig-py

Python bindings to fontconfig

fontconfig-py

Python bindings to fontconfig based on Cython.

Currently, Linux and macOS are supported.

Install

Install from the PyPI:

pip install fontconfig-py

Usage

The following demonstrates the usage of fontconfig.query to identify English fonts in the system:

import fontconfig

fonts = fontconfig.query(where=":lang=en", select=("family",))
for font in fonts:
    print(font["family"])

Development notes

There are other Python wrappers for fontconfig:

• fontconfig: CFFI bindings for fontconfig
• python_fontconfig: Python wrapper based on ctypes
• Python_fontconfig: Unmaintained Cython wrapper

The features of this package are the following:

• Cython-based wrapper
• Statically linked binary wheels; no runtime dependency
• Continuous integration to the PyPI distribution
• User documentation
• MIT license

License notice

This project is distributed under MIT license. The binary wheels link fontconfig and freetype which are distributed under different licenses. See THIRD-PARTY-NOTICES.txt.

fontconfig-py's Issues

Set up documentation

Set up sphinx documentation for the project. The documentation should describe:

• Overview
• Install
• Usage
• API reference
• License

This project bundles freetype2, and perhaps that requires having the FTL.txt license file somewhere in the document directory.

fontconfig version issue in the readthedocs environment

Currently, the build process in the readthedocs depends on the fontconfig system package, and that introduces version mismatch with the bundled fontconfig. This causes some APIs missing from the package (#17). Needs to investigate whether it's possible to install the package in the readthedocs environment.

Error cannot load default config file

Simply after installing in a venv I tried to open a shell and try import fontconfig and I get the following error:

Fontconfig error: Cannot load default config file: No such file: (null)

I'm on arch linux and using fontconfig version 2.14.2-1 if it helps.

Is this expected behavior ? It seems weird to get this log using a library for the first time.