Kobo Bug thread

[PenguinCEO]

Originally Posted by davidfor

... as you are again treating me as an idiot ...

You have lost your calm and your reason. You continue to swear and you have reduced this forum to a pigsty.

Originally Posted by davidfor

So important that the only screenshots you can find about the issue are the ones you posted.

How many do they need?

Originally Posted by davidfor

So important that it is a topic that has rarely been discussed here.

How many times does it needs?

Originally Posted by davidfor

So important that no-one seems to have reported the error in the standard paths as a bug.

What seems to you may not be the truth.

Originally Posted by davidfor

There is no bad logic, the "problem" was removed in design.

Here everybody has understood that you are wrong. The logic is wrong. And kobo did wrong the design. Now stop responding if you only need to communicate your personal opinions or deliriously shout bad words.

[JSWolf]

Can anyone name one other version of RMSDK that does not support a monospace font other then Kobo?

[davidfor]

Originally Posted by JSWolf

Can anyone name one other version of RMSDK that does not support a monospace font other then Kobo?

That isn't the question. And it definitely isn't the claim that you have been making. There is only one RMSDK (yes, there are multiple versions released over time, but, there is only one source for it). There are multiple devices or applications that use it. The monospace fonts are added by the device or app developers. Or they rely on the OS to supply the font.

[davidfor]

Originally Posted by PenguinCEO

You have lost your calm and your reason. You continue to swear and you have reduced this forum to a pigsty.

Were have I sworn? Exactly how have I turned this forum into a pigsty? Please tell me as, while I am displeased with the way @Rev. Bob seems to be treating me, at no time have I sworn or used any other type of bad language. And honestly, I'm a lot more displeased with your attacks. If I was going to lose my calm and reason, or swear, it would be at you.

How many do they need?

How many times does it needs?

You are the one trying to say how important this feature is. And yet, the only evidence that you have for this is your posts. I had a look at the posts in this forum, it has hardly been discussed. I had a look at my books, others have looked at their books. The number off books we can find that need this function is minuscule.

Then there are the absolutely huge number of people clamouring for Kobo to implement this. (And to be clear, there is no swearing in that statement, just some sarcasm.)

Most people will not have even noticed it was missing. That means it is not very important to many people. 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.

What seems to you may not be the truth.

Yes, I believe that no-one had previously reported the error in the font path. Can you give me a reason why I'm wrong?

Here everybody has understood that you are wrong. The logic is wrong.

That is impressive. There isn't any code to do something, so it is wrong. Now that is impressive logic.

And kobo did wrong the design. Now stop responding if you only need to communicate your personal opinions or deliriously shout bad words.

I'm not allowed to express my opinion? I thought that was the point of a discussion. Or is it just when I disagree with you? I mean, everything you have posted above is your personal opinion. Especially where you are accusing me of using bad words, deliriously or not.

[DNSB]

Originally Posted by PenguinCEO

You have lost your calm and your reason. You continue to swear and you have reduced this forum to a pigsty.

argumentum ad hominem: typically refers to a fallacious argumentative strategy whereby genuine discussion of the topic at hand is avoided by instead attacking the character, motive, or other attribute of the person making the argument, or persons associated with the argument, rather than attacking the substance of the argument itself.

A technique generally beloved of those who do not have logic or facts on their side of the argument.

Originally Posted by PenguinCEO

Here everybody has understood that you are wrong. The logic is wrong. And kobo did wrong the design. Now stop responding if you only need to communicate your personal opinions or deliriously shout bad words.

Perhaps you could define a meaning of everyone where even one person disagreeing with you would not render your statement invalid?

I find it curious that you feel posting your personal opinion is valid but others are not permitted to post dissenting opinions. I would truly love to see a definition of "deliriously shout bad words" that would include the contents of any of davidfor's posts in any Mobileread forum.

“If the facts are against you, argue the law. If the law is against you, argue the facts. If the law and the facts are against you, pound the table and yell like hell” —Carl Sandburg

[PenguinCEO]

Originally Posted by davidfor

And yet, the only evidence that you have for this is your posts.

Do you say It's one evidence?. One evidence is enough.

Originally Posted by davidfor

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.

Originally Posted by davidfor

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.

Originally Posted by davidfor

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.

Originally Posted by davidfor

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.)

[PenguinCEO]

Originally Posted by DNSB

...

querulous: Complaining in a rather petulant or whining manner. (Oxford dictionary)

[MGlitch]

Originally Posted by PenguinCEO

Do you say It's one evidence?. One evidence is enough.

That the issue exists? Sure. But no one is denying that monospace fonts aren’t on kobo devices.

"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.

Oh please spare us the quibbling over minuscule being an opinion. Others have posted in your other thread that the books with monospace fonts at all makes up 0.01% of their library. That’s minuscule from the layman’s viewpoint as well as many others.

"most people", "many people" and "not very important" are opinions. The fact is that monospaced text is not implemented.

And kobo is a company with limited resources. It doesn’t make sense to ignore say 1000 people asking for certain features in favor of 0.1 person asking for it (using the monospace in libraries statistics from above). Look even when you brought it up the overwhelming response is at best ‘technically this is a bug and kobo should probably fix it’ with exceptionally few saying it’s actually an important feature to them. Bob for all his prattling hasn’t even said it’s important to him that Kobo does anything just that his interpretation says they must (despite the specs he quotes literally contradicting him). You are the only one who seems to care personally about this being added.

[quote
Now I could be sarcastic and mention the crystal ball in which you read that news, but I will not do.
[/quote]

It doesn’t take a crystal ball. Though it likely requires more deductive skills than you’re willing to exercise. Kobo puts out updates on a fairly frequent basis they are open to feedback and have implemented changes requested by users as well as fixed bugs reported by users. That they haven’t added monospace would indicate few requests for it at best.

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. a 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.

I’ll put aside that you whined when minority was used and yet have no issues invoking majority.

Here’s another thing the majority of people don’t care about: monospaced fonts.

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

Luckily we’re not living in a world defined by a software developer. Words exist for a reason.

The product works as Kobo wants it to.

The product is deficient in the views of an incredibly small and commercially insignificant minority of their customers.

[Terisa de morgan]

Originally Posted by PenguinCEO

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".

Well, majority, majority.... Let's say that I seriously doubt that a lot of people know what a "standard epub" is. I really, really doubt majority of people know there is a standard. And "bona fide" modifying specs? Well, good luck with that (and yes, it's modifying the specs as all the previous discussion has been based on a gramatical point, difference between should and must).

And, additionally, I can imagine my reader friends' face if I ask them if they have been aware of the lack of a monospaced font. The first question will be: what is that?

[JSWolf]

Originally Posted by davidfor

That isn't the question. And it definitely isn't the claim that you have been making. There is only one RMSDK (yes, there are multiple versions released over time, but, there is only one source for it). There are multiple devices or applications that use it. The monospace fonts are added by the device or app developers. Or they rely on the OS to supply the font.

Given that Sony used both Linux and Android and nook uses Android, if it is the OS supplying the font, then where is it in Kobo as it also runs Linux?

And as was pointed out, the code for monospace is n RMSDK. So if it's not part of RMSDK, why is the code there?

[Rev. Bob]

Originally Posted by Rev. Bob

In this situation, I don’t think you correctly understand the context. Doesn’t make you an idiot, just not a specialist… and in this case, I am a specialist. Similarly, if my car breaks down, I’m damned near useless and have to employ a mechanic for anything more involved than adding fluids or changing wiper blades.

Originally Posted by davidfor

Sorry Rev, but based on your responses, especially that first one, have been that you are of that opinion.

So, despite me explicitly telling you something, you choose not to believe me.

Originally Posted by davidfor

Is because they told me good enough?

By your own standards, clearly not.

Originally Posted by davidfor

And to the mods, I'll stop after this post.

Not much point in me responding to the rest of your post, then… or any of the subsequent ones you made on the subject.

PenguinCEO’s right. You have lost your calm and your reason.

[Rev. Bob]

Originally Posted by PenguinCEO

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.

Monospace styling is fairly common in SF in general and the rendering of code, emails, or text messages in pretty much any genre. Great way to convey that something is being displayed on a device display.

And that doesn’t even get into programming manuals. Those positively love to use monospace to display properly-indented code samples.

[PenguinCEO]

Originally Posted by Terisa de morgan

...

I am enchanted by your grace and your kindness in answering me, so accept a bouquet of roses.

Originally Posted by Terisa de morgan

Let's say that I seriously doubt that a lot of people know what a "standard epub" is.

You are right, this is a matter for specialists. But common sense is enough to understand what "correctly rendered document" means. I'm not a professor of surgery, but I know the difference between "feeling good" and "being sick".

Originally Posted by Terisa de morgan

And, additionally, I can imagine my reader friends' face if I ask them if they have been aware of the lack of a monospaced font. The first question will be: what is that?

You are right. Your friends don't read computer books.Well, ask them "What is an epub-reader?". They will give you an acceptable answer. Then ask them "And what is the minimum that should be expected from an epub-reader?" Each of them will answer you with a round of words that, with good approximation, means "reproduce a standard epub in a standard way".

Computer books are books with full cultural and scientific dignity. You would not accept that your computer books were printed on waste paper just because they are fewer in number than fiction books. Indeed, you (and your friends) certainly expect that the major typographic complexities of your technical books are correctly returned by more accurate technical details. And if someone told you that this is a singular and elitist claim you would feel teased.

Attachment 174724

Similarly, it is not acceptable to be told that this is the "normal" way to reproduce a book. This result is far below the acceptable minimum (and your friends would agree with me).

[issybird]

Moderator Notice
Two points:

Time to get back on topic. This is the bug report thread. Report a bug and move on. Further discussion of monospace should be taken to the dedicated thread. Any more comments about monospace in this thread will be deleted.

Stop playing "gotcha" and posting derogatory posts directed at other members. Further posts along those lines in this thread will also be deleted.

[issybird]

One more comment: Manners. Terms such as "pigsty" are not to be employed, and most especially from newbies with a handful of posts directed at a long-term and highly valued member. Several others need to dial it back. Thanks.