Currently, custom fonts in the EPUB navigator can only be provided through the assets folder. This is inconvenient for Android apps because fonts are commonly stored in res/font, where they can be reused from XML layouts, views and composables.
As a result, apps that want to use the same font in both their Android UI and Readium need to duplicate the font in both res/font and assets.
It would be useful for Readium to support declaring custom font families from Android font resources, including both single font files and XML font family resources.
Currently, custom fonts in the EPUB navigator can only be provided through the assets folder. This is inconvenient for Android apps because fonts are commonly stored in res/font, where they can be reused from XML layouts, views and composables.
As a result, apps that want to use the same font in both their Android UI and Readium need to duplicate the font in both res/font and assets.
It would be useful for Readium to support declaring custom font families from Android font resources, including both single font files and XML font family resources.