Oleg Oshmyan

That sounds like Fontconfig’s cache building. It should happen only once, when you first run your libass-enabled FFmpeg. Subsequent starts should be quick.

libass uses Fontconfig to find and choose fonts for rendering subtitles. It builds a cache of all fonts installed on the system so that when libass (or other consumer) looks...

I’m getting dangerously close to wasteful bikeshedding, but: Given that the original motivation was to provide accurate bitmap boundaries, isn’t naming it `...LARGE_SCREEN` or `...HIGH_DPI` kinda missing the point? @MrSmile...

How does this relate to #312? See also my own plans/hopes for reworked font providers in https://github.com/libass/libass/pull/511#issuecomment-873572826. > First, we should attempt to find a match using memory fonts only,...

Hang on, so is it fine with HarfBuzz? Thanks a lot for the triage!@rcombs, are OP screenshots not yours? Shame on you for not checking whether HarfBuzz was enabled 😅😅If...

`kCTFontFormatOpenTypePostScript` is required for compliant system font handling. You can use libass with the suggested patch, and most functions will work fine. Only if you play a file that fails...

As for: > wrong number of arguments specified for ‘deprecated’ attribute Which compiler is that? The LLVM-backed GCC, or an actual early Clang? We’d be happy to add a check...

> The log from the OP suggests it’s GCC 4.2 and indeed […] Right, thanks. I’d misread our code and incorrectly assumed that we already handled real GCC’s versioning and...

> I have built it now with `--enable-test`, but need to figure out how to use it. I believe you just pass in a target output PNG image file path,...

Thanks! Not sure why `font format: 3` is printed twice, but it seems clear enough to conclude the following: * Interestingly enough, Type 1 fonts are actually accessible via this...