Thread: Kobo Bug thread
View Single Post
Old 11-14-2019, 09:23 PM   #1183
MGlitch
Wizard
MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.MGlitch ought to be getting tired of karma fortunes by now.
 
Posts: 2,857
Karma: 22003124
Join Date: Aug 2014
Device: Kobo Forma, Kobo Sage, Kobo Libra 2
Quote:
Originally Posted by Rev. Bob View Post
By that logic, there’s no such thing as a bug. In every case, the software is behaving as the programmer lets it.


Not even remotely true, a bug is when software does something the programmers don't want, such as crashing, not opening something, or as was introduced in 4.18 not properly updating the time remaining in reading progress.

A deficiency is when the program does not do something that some may reasonably expect it to do, such as displaying monospace fonts in this case.

Those books that use them are still readable, though slightly harder, save perhaps for specific languages. I wouldn't be able to comment on how a vertical language would be affected here. Or if it were unable to change fonts, we the user may find it deficient given this is a feature we have come to expect from virtually ever ereader.

I wouldn't have thought the difference need be explained to someone in a technical field where semantics are important because <blah> is not the same as {blah} nor [ blah]
MGlitch is offline   Reply With Quote