Aura H2O Referencing internal fonts?

[Ghitulescu]

Pardon me if this subject has been discussed before, inspite my good will and long searches I could not find a way to reference the internal fonts (Georgia, Amasis etc) in the CSS.
Has anyone any idea what the path looks like?
To be clear: I don't want to use "Change default font to XYZ" from the menu, but to edit ePubs to pick one of the internal fonts.

[GeoffR]

This post has an example, it works the same for built-in and sideloaded fonts.

[Ghitulescu]

The question is asked, because I want to get an H2O.
Therefore I don't have one and I don't know many implementation details.

For one, I noticed that most font-related topics contain the instruction "...create a folder named fonts in the root...". That means that either the fonts does not exist or the path to internal fonts is different.

[GeoffR]

Originally Posted by Ghitulescu

The question is asked, because I want to get an H2O.
Therefore I don't have one and I don't know many implementation details.

For one, I noticed that most font-related topics contain the instruction "...create a folder named fonts in the root...". That means that either the fonts does not exist or the path to internal fonts is different.

The built-in fonts such as Georgia are stored on the system partition, the sideloaded fonts are on the user partition in /fonts, but both are referenced in the same way. ('res:///fonts' is a symbolic reference to all locations that might have fonts, not just to the /fonts directory; 'res:///fonts/normal' refers to normal weight fonts, there is no actual directory called /fonts/normal.)

Edit: I just tested it on my Glo with firmware 3.12.0, and it still works the same way. As an example: @font-face {font-family: Amasis; font-weight: normal; font-style: normal; src: url('res:///fonts/normal/Amasis')}, etc. references the built-in Amasis font, and then body {font-family: Amasis;} will make Amasis the default font for the book.

[Ghitulescu]

Thank you.

Everything is now clear.

[scoky]

According to my test results, this method only supports epub and can't support kepub...
I find this solution for kepub in this post
https://www.mobileread.com/forums/sho...35&postcount=6

[GeoffR]

Originally Posted by scoky

According to my test results, this method only supports epub and can't support kepub...

I tested on my Glo with a sideloaded kepub, and the epub 'res:///fonts' method worked for the kepub too. (I didn't use Calibre to make the kepub, just copied the .epub to .kepub.epub)

Edit: After further testing, I see the 'res:///fonts' method doesn't work with kepubs for some fonts. e.g. Amasis works for both epub and kepub, but Avenir only works in epub.

[scoky]

Originally Posted by GeoffR

I tested on my Glo with a sideloaded kepub, and the epub 'res:///fonts' method worked for the kepub too. (I didn't use Calibre to make the kepub, just copied the .epub to .kepub.epub)

Edit: After further testing, I see the 'res:///fonts' method doesn't work with kepubs for some fonts. e.g. Amasis works for both epub and kepub, but Avenir only works in epub.

If I only use "font-family: XXXX;" (XXXX is the font name in Font Face of Aa setting) to use sideload fonts, it can work perfectly. So the kepubs don't need to be specified the font path.
However, if I use your method like this
@font-face {font-family: "zw"; font-weight: normal; font-style: normal; src: url('res:///fonts/normal/XXXX')} and font-family: XXXX,
it only work correctly in epubs and not in kepubs.