This is essentially a stripped-down version of FontConfig compiled to WebAssembly with a Javascript API that works in nodejs and the browser.
import FontConfigInit from 'fontconfig';
import fs from 'fs';
const FontConfig = await FontConfigInit(/* wasm URL if you're in the browser */);
const cfg = new FontConfig();
const fonts = [
'/Library/Fonts/Comic Sans MS.ttf',
'/Library/Fonts/Futura.ttc',
'/Library/Fonts/GillSans.ttc'
];
for (const filename of fonts) {
cfg.addFont(new Uint8Array(fs.readFileSync(filename)), filename);
}
cfg.sort({
family: 'Gill Sans',
weight: FontConfig.FC_WEIGHT_LIGHT
});
// returns this:
[
{ file: '/Library/Fonts/GillSans.ttc', index: 7 },
{ file: '/Library/Fonts/GillSans.ttc', index: 6 },
{ file: '/Library/Fonts/Comic Sans MS.ttf', index: 0 },
{ file: '/Library/Fonts/Futura.ttc', index: 2 }
]
Unlike the full FontConfig library, it does not read configuration files for font lookup rules or font search directories. The part of FontConfig for adding and querying fonts (the matching module) is exposed instead, which the Javascript wrapper makes calls to. At some point support for FontConfig rules and aliases (the configuration module) could be added. I don't expect it to be very useful since consumers of this library are typically adding and selecting fonts on their own, rather than users doing it.
Instead of using FreeType to read fonts, fontkit is used.
Returns the best possible cascade list of fonts based on a description (with later fonts suited to use when previous fonts don't have proper coverage).
The pattern object passed to FontConfig.prototype.sort
looks like:
family
(string|string[]) (required)weight
(number|string) (a CSS2 weight like'200'
orFontConfig.FC_WEIGHT_EXTRALIGHT
)width
(number|string) (a CSS3 width like'condensed'
orFontConfig.FC_WIDTH_CONDENSED
)slant
(number|string) (a CSS2 slant like'oblique'
orFontConfig.FC_SLANT_OBLIQUE
)lang
(string|string[])coverage
(number[])
When the family
is an array of more than one family, it is a prioritized list. If the first family isn't found, FontConfig tries the second family. If more than one is found, they will all appear in the results in prioritized order.
For more details on other properties' individual values, continue below.
Note you can also use CSS2 font-weight
values as a string like '300'
FontConfig.FC_WEIGHT_THIN
FontConfig.FC_WEIGHT_EXTRALIGHT
FontConfig.FC_WEIGHT_ULTRALIGHT
FontConfig.FC_WEIGHT_LIGHT
FontConfig.FC_WEIGHT_DEMILIGHT
FontConfig.FC_WEIGHT_SEMILIGHT
FontConfig.FC_WEIGHT_BOOK
FontConfig.FC_WEIGHT_REGULAR
FontConfig.FC_WEIGHT_NORMAL
FontConfig.FC_WEIGHT_MEDIUM
FontConfig.FC_WEIGHT_DEMIBOLD
FontConfig.FC_WEIGHT_SEMIBOLD
FontConfig.FC_WEIGHT_BOLD
FontConfig.FC_WEIGHT_EXTRABOLD
FontConfig.FC_WEIGHT_ULTRABOLD
FontConfig.FC_WEIGHT_BLACK
FontConfig.FC_WEIGHT_HEAVY
FontConfig.FC_WEIGHT_EXTRABLACK
FontConfig.FC_WEIGHT_ULTRABLACK
Note you can also use CSS3 font-stretch
values as a string like 'condensed'
FontConfig.FC_WIDTH_ULTRACONDENSED
FontConfig.FC_WIDTH_EXTRACONDENSED
FontConfig.FC_WIDTH_CONDENSED
FontConfig.FC_WIDTH_SEMICONDENSED
FontConfig.FC_WIDTH_NORMAL
FontConfig.FC_WIDTH_SEMIEXPANDED
FontConfig.FC_WIDTH_EXPANDED
FontConfig.FC_WIDTH_EXTRAEXPANDED
FontConfig.FC_WIDTH_ULTRAEXPANDED
Note you can also use CSS2 font-style
values as a string like 'italic'
FontConfig.FC_SLANT_ROMAN
FontConfig.FC_SLANT_ITALIC
FontConfig.FC_SLANT_OBLIQUE
An RFC3366 language tag such as "en"
or "zh-tw"
The coverage
option is an array of unicode codepoints. For example, if you pass {coverage: [0x1780]}
, a Khmer font will be at the top of the list.
Thanks to WASI, you can set the environment variable FC_DEBUG
1 just like regular font config. This will print information to stdout, but only if
- You built with
-DWASI_RUNTIME
(see below) - You're using nodejs 13.3.0 or newer
- You run nodejs with
--experimental-wasi-unstable-preview1 --experimental-wasm-bigint
The WASM distributed in NPM is not built with debugging calls, though there are probably WASI runtimes available for web browsers.
1As of node 13.10 this doesn't seem to be implemented yet, so you have to manually edit src/fcdbg.c
until it's fixed.
Make sure you clone with --recurse-submodules
These instructions are for macOS, but they should be similar for Linux. The steps are familiar to anyone who has done cross-compilation before, but the first few are WebAssembly-specific.
cd fontconfig; patch -p1 < ../pure-wasm-compat-fontconfig.patch; cd..
LLVM_PATH=/usr/local/Cellar/llvm/9.0.0/bin
. or somewhere else appropriate. You do need a recent version of LLVM that supports WebAssembly.git clone git@github.com:chearon/wasi-libc.git
. The upstream version builds with symbols that introduce runtime dependencies.cd wasi-libc
make WASM_CC=$LLVM_PATH/clang WASM_AR=$LLVM_PATH/llvm-ar WASM_NM=$LLVM_PATH/llvm-nm
WASI_SYSROOT=$(pwd)/sysroot
- Download
wasi-sdk
builtins and copylibclang_rt.builtins-wasm32.a
to/usr/local/Cellar/llvm/9.0.0/lib/clang/9.0.0/lib/wasi/
(or wherever you installed your compiler in step 1). export LIBTOOLIZE=glibtoolize
(these next 3 steps might be macOS-specific)export GETTEXTIZE=/usr/local/opt/gettext/bin/gettextize
export AUTOPOINT=/usr/local/opt/gettext/bin/autopoint
export CC=$LLVM_PATH/clang
export CFLAGS=-target wasm32-wasi --sysroot=$WASI_SYSROOT
(for debugging, you can also add-DWASI_RUNTIME
to see FontConfig logging)export AR=$LLVM_PATH/llvm-ar
export RANLIB=$LLVM_PATH/llvm-ranlib
- Patch config.sub:
grep -q -F -- '-wasi' config.sub || sed -i -e 's/-nacl\*)/-nacl*|-wasi)/' config.sub
(thank you so much, Frank Denis) ./autogen.sh --host=wasm32-wasi
make
$LLVM_PATH/wasm-ld -L$WASI_SYSROOT/lib/wasm32-wasi --no-entry --export-all -lc --whole-archive src/.libs/libfontconfig.a -o ../packages/core/lib.wasm