Thread: Kobo Bug thread
View Single Post
Old 11-15-2019, 05:30 AM   #1189
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by JSWolf View Post
Yes, there is a bug and this is it...

From librmsdk.so.1.0.0:
res:///fonts/CourierStd.otf
res:///fonts/CourierStd-Bold.otf
res:///fonts/CourierStd-Oblique.otf
res:///fonts/CourierStd-BoldOblique.otf

Should be...
res:///fonts/normal/CourierStd.otf
res:///fonts/bold/CourierStd-Bold.otf
res:///fonts/italic/CourierStd-Oblique.otf
res:///fonts/bolditalic/CourierStd-BoldOblique.otf

Because of this, CourierSTD cannot be put in fonts and used when monospace is used.
So the only possible bug is that Kobo has some paths inconsistent with their other font paths. The one that I have commented about several times. So the way Kobo have "botched" the RMSDK is by putting in the wrong path. A path that doesn't actually point to anything that they were planning to supply. Or was mandatory for them to supply.
davidfor is offline   Reply With Quote