mikehaertl
commented
6 years ago I now also tried with your base image and the following HTML. The font is rendered as sans-serif. There are serif fonts installed and fontconfig finds them. So I'd say it must have to do with wkhtmltopdf:
<!DOCTYPE html>
<html>
<head>
<style>
p {
font-family: "Times New Roman", Times, serif;
}
</style>
</head>
<body>
<div style="font-face: serif; font-size: 12px">
A little test.
</div>
<p>Another paragraph.</p>
</body>
</html>
chdanielmueller
ashkulz
I've included your
wkhtmltopdfbinary into one of my Alpine 3.7 based images like this:It works fine so far, except for one nasty issue: It seems to ignore any
font-familysettings in the generated PDF. Is this a known problem? If not, any idea what I'm doing wrong or what else I could try?More background:
I'm migrating an older Debian based application with wkhtmltopdf 0.11 to an Alpine based image. The old app works just fine, whereas the new one fails to render the correct font. The relevant part of the CSS is:
As I understand it, wkhtmltopdf asks fontconfig to deliver a matching font file. So far I found out, that in the end the old app uses the
n021004l.pfbfont file. This is the font recommended by fontconfig. The font is also available under the new app and listed there underfc-list. So I used FC_DEBUG=1 to see what wkhtmltopdf asks for and what fontconfig sends back in return.The output is listed below. The top block seems to be the "query part" (AKA what wkhtmltopdf asks for). And the lower block (Best score ...) is, what fontconfig thinks is the best match for this query.
The weird thing is, that with 0.12.4 it always queries the same list of font families (family: "Helvetica"(s) "TeX Gyre Heros"(s) "Arial"(w)...) , no matter what I set in CSS. Whereas in the old app the query is much more in line with my CSS (family: "Times New Roman"(s) "Tinos"(s)..).
Any feedback is appreciated.
Fontconfig output from the old app
Fontconfig output from the new app