|
@Rev. Bob: I have read what I need to of you reply and have the following comments:
Firstly, all specs are up to the interpretation of the developers involved. And unless they say that something must be done in a particular way, then what is done will be up to the interpretation of the developer. I do not not read any of these as saying must. "Should" does not mean "must". And no, I am not interpreting "should" as "may". I am interpreting "should" as "should". And that means "It would be a damn good idea if you did this, but, you don't absolutely have to do it".
My comment about epub 2 was because you supplied links to CSS for epub3 and epub2. They were different links. I read both. They were not identical. The text is very different and in no way was it word-for-word the same. If you pointed to the wrong thing, then you should have said that rather than accusing me of not being able to read.
Yes, my comment about how rarely I have seen monospace is anecdotal, as is yours. An no, neither proves that anything other than we have different book. But, do you really believe that books that need monospace in them are actually a significant percentage of all books out there? Kobo have got the stats based on all the books they see. They don't see this is important to them.
For the record, I was surprised when I first realised that there was no monospace font supplied. But, I've never considered it a bug. I see it as a missing feature, and not a particularly important one. I can list a lot of things I'd like to see on the device before this. And, as I always say at this point, if you have a problem, report it to Kobo. If you don't, then there is no reason for them to fix or change something as it is obviously not important to you.
|