During the migration from v3 to v4, a difference was found in the rendering of fonts. Looks like V4 only supports one default font out of the box.
output_v3.pdf (68.8 KB)
output_v4.pdf (11.0 KB)
input.html.zip (792 Bytes)
@vladimir.kozhaev
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): HTMLCLOUD-2163
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
In reference to your above reported issue, please note that commercial fonts require a license, so we did not include the fonts in the V4. However, if you want to use your own custom fonts in the conversion, then as an option, you can upload the fonts to your own server (for example to AWS S3) and link the font in CSS, as in the example:
@font-face {
font-family: myTahoma;
src: url(https://clientserver.com/tahoma.woff);
}
div {
font-family: myFirstFont;
}
Similarly, any font from CDN can be used. For example, all Google web fonts that are free to use.