View Single Post
Old 05-16-2020, 12:28 PM   #10
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,960
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by pepak View Post
I had a look at these patches, but it seems they are only intended for the built-in fonts, aren't they?
AFAIK, they also work with the add-on fonts. As noted in the patch files:
Code:
    # to another font name prefix (7 letters max.). For example, change "Amasis"
    # to "Times" to use a sideloaded Times New Roman font.
Quote:
Originally Posted by pepak View Post
That is of course a mistake. This is actually my 11th version of the test, one which involved adding those spans (because I read in a thread that otherwise the default rules on <p> tags would take over), and apparently forgot to overwrite the second and third one. But after a quick check, even that doesn't get me the right fonts.
Your font-family setup in page-styles.css was also incorrect. I attached a fixed up version to the previous message. At least, it works on my Forma with Publisher Default selected.
DNSB is offline   Reply With Quote