Thread: Kobo Bug thread
View Single Post
Old 11-16-2019, 11:53 AM   #1211
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: 47,053
Karma: 169810634
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Rev. Bob View Post
And that’s why I say that Kobo’s omission of a monospace font is a bug. They licensed an engine which includes such a font: the Adobe RMSDK. Their hardware is demonstrably capable of rendering monospace. Their devices have ample memory to store the font. Even if it were a matter of licensing fees, there are monospace font families which are free for commercial use; a quick search yields several. Surely at least one of them is aesthetically acceptable and reasonably complete.
An interesting claim that RMSDK includes a monospace font. Support for monospace fonts is a definite yes but actually including a monospace font? The last time I looked at the Datalogics RMSDK documentation for v11.0, the phrases "device resident" and "system fonts" was used with no mention of any fonts being supplied with the SDK.
DNSB is offline   Reply With Quote