Hello Mike,
Sorry for the late reply. >> Please try the new 2.26 version! We don't apply any fixes to the >> 2.24 series. Note in particular that the font selection has >> changed. The simplest cases should be covered by `convert-ly`, but >> more complicated situations might need additional manual work. > > Still present in version 2.26. I've now checked your files and can confirm the problem. The code in function `All_font_metrics::add_font_directory` simply passes the relative directory name to FontConfig. However, LilyPond has already changed the working directory according to the value of the `--output` command-line option, causing the problematic behaviour you are observing. The whole situation gets exacerbated because `lilypond -V` doesn't give any information about user-added font directories – it seems that directories added with `FcConfigAppFontAddDir` are not shown with `FcConfigGetFontDirs`, see https://lists.freedesktop.org/archives/fontconfig/2026-June/007350.html So: please file an issue at https://gitlab.com/lilypond/lilypond/-/work_items but use a freely available font instead of Minion Pro for the example code. Werner
