|
i have similar issues with bookerly , but in a different app/ device ( mantano on Fire tablet). yet on PC, in word for example the bookely font works in all bold and/or italic modes, as it should, likewise in the amazon fire app
I noticed the mismatch within names, and I checked other fonts.
I saw that both bookerly and drioid-Serif append regular within the file name. most other fonts do not
so the majority of font sets go name.ttf, name-bold.ttf, name-italic.ttf...
but a minority use name-regular.ttf, name-bold.ttf ....
and some font sets appear as a single instance not as a set of 4 ?
i would have thought that internal names would exist within the files, rather than a dependence on file name ?
I also noticed that adding / removing "regular" to standardise the name was having some effect but I ran out of testing patience before logically working through all combinations
so what are the rules for how set should / must? be named in order to work
my final example. I think that my mantano app sees bookerly-regular and bookerly-bold as two different fonts , because of the broken naming convention. yet it has no trouble with driod serif which is named similarly...
most puzzling ?
i want to have a master set of fonts so that all my reading options - kobo, fire.,voyage.. have same font choices but bookerly is not playing nice or consistently
|