Thread: Kobo Bug thread
View Single Post
Old 11-17-2019, 03:37 PM   #1221
PenguinCEO
Member Retired
PenguinCEO knows more than wikipediaPenguinCEO knows more than wikipediaPenguinCEO knows more than wikipediaPenguinCEO knows more than wikipediaPenguinCEO knows more than wikipediaPenguinCEO knows more than wikipediaPenguinCEO knows more than wikipediaPenguinCEO knows more than wikipediaPenguinCEO knows more than wikipediaPenguinCEO knows more than wikipediaPenguinCEO knows more than wikipedia
 
Posts: 61
Karma: 47166
Join Date: Sep 2018
Device: a lot
Quote:
Originally Posted by davidfor View Post
And yet, the only evidence that you have for this is your posts.
Do you say It's one evidence?. One evidence is enough.

Quote:
Originally Posted by davidfor View Post
The number of books we can find that need this function is minuscule.
"Minuscule" is an opinion. The fact is that everyone who has looked into his own library for monospaced text has found some examples of it (you too). For the record I too have four technical books and one french novel using monospace.

Quote:
Originally Posted by davidfor View Post
Most people will not have even noticed it was missing. That means it is not very important to many people.
"most people", "many people" and "not very important" are opinions. The fact is that monospaced text is not implemented.

Quote:
Originally Posted by davidfor View Post
And if they were asked by Kobo whether to add a monospace font or some other function, they will probably not ask for the monospace font.
Now I could be sarcastic and mention the crystal ball in which you read that news, but I will not do.

Quote:
Originally Posted by davidfor View Post
That is impressive. There isn't any code to do something, so it is wrong. Now that is impressive logic.
It is quite simple, free up your brain from coding and try to fly a bit higher. kobo offered me an epub-reader, that is an object that, according to the common way of thinking of the absolute majority of people, is a device destined to reproduce epub files. Epub in the sense understood by the majority of people (not only experts of xml, css and rmsdk), i.e. standard epub. Now if the device that was sold to me is not able to reproduce a standard epub, kobo cannot justify itself by saying that its secret project does not include the complete implementation of css. The sale is a contract, the contract must be interpreted according to good faith. The bona fide interpretation says that where the standard says that an epub-reader "should" provide monospaced fonts we must mean "must".
And if it does not, well, it's buggy, because if the project is buggy then also the software that perfectly implements that project is bugged.

(Incidentally: Out of the community of software developers there is no difference between "bug" and "deficiency". They are both errors that must be corrected.)

Last edited by PenguinCEO; 11-17-2019 at 04:18 PM.
PenguinCEO is offline   Reply With Quote