G'day... I'm having (no end of) trouble trying to get a custom font to work with cfdocument. I think it was working a few months ago but it has been a work in progress so I'm not 100% on that one. More info in thread...

see the link i posted? https://dev.lucee.org/t/utf-8-fonts-in-pdf/13056/5

I mentioned "PDF ext v1.1.0.19" earlier and have just tried 1.2.0.10-RC with the same result.

but the naming as per mentioned in the linked issue

yes, also mentioned above - font-family name and font file name share the same case.

classic or modern?

What does that mean? I've seen it mentioned but assumed it referred to the version if the PDF extension.

there are two pdf engines in the pdf extension

it must be 'modern' - I don't set it and that is the default

for this and create a test case? https://github.com/lucee/extension-pdf/blob/master/tests/LDEV3836.cfc

@brettpr I don't use the PDF extension (we use wkhtmltopdf) but a few things I'd check: • Look through your logs to see if you can find any exceptions being thrown. • Check the permissions on the fonts. Maybe Lucee doesn't have permissions to read them, so it's not picking them up.

sigh - it is the font file itself... it works in the browser but the PDF engine doesn't like it for some reason. I worked this out by trying an alternative custom font which worked ok... 🙄

@brettpr Just to confirm, the file permissions (r/w and user/group) are the same as the font that does work?

@dswitzer - yes, all are the same. The font file works for html rendering and when installed on my PC - but not when included with cfdocument.

Maybe something like this might reveal something: https://github.com/HinTak/Font-Validator/

I've also tried wkhtmltopdf and that also works and am heading down the path of trying that on a test server

One of the "pluses" in my book for wkhtmltopdf is because it runs outside of the JVM, we didn't need to worry about JVM memory heap issues when processing large HTML documents, which used to be a problem. I wish there were more work done to keep the tool updated with Chromium, but it still works pretty good.

@dswitzer - the font testing tool is awesome, thank you! I obviously didn't look deeply enough when I searched for font testing tools. The font file is indeed faulty, I guess in some way that seems to only matter to the PDF engine used by Lucee.

@brettpr I suspect other tools would have issues too, but glad you found the root issue. That's why I thought it might be a permissions issue, since other fonts worked. I thought maybe something was preventing the JVM from loading the font.