Aura ONE "monospace" rendering

[PenguinCEO]

I have a KA1

An ebook of mine has the following html code:

<div class="example">
<pre class="example">    --- ---      --- ---      --- ---
   |   |   |--&gt; |   |   |--&gt; |   |   |--&gt; nil
    --- ---      --- ---      --- ---
     |            |            |
     |            |            |
      --&gt; rose     --&gt; violet   --&gt; buttercup
</pre></div>

with the following css code

div.example {
  margin-left: 3.2em;
  font-family: monospace;
}
pre.example {
  font-family: monospace;
}

The book was made in epub format with the calibre editor and converted in kepub with calibre.

The above code is rendered exactly by the calibre viewer, as you can see in the images





but is poorly rendered by the aura one: as you can see the "monospace" attribute is lost





Is there something to do to solve this problem?

[JSWolf]

What you need to do is patch the firmware to fix a bug where monospace doesn't work. By doing this, monospace will work.

[jackie_w]

Originally Posted by PenguinCEO

Is there something to do to solve this problem?

The answer is 'yes' but whether the effort involved in the solution will be acceptable to you is another matter. The solution is different depending on whether you are going to read the book as a kepub or a standard epub on your Kobo.

You mentioned kepub above so steps 1-3 in this post should give you some pointers.

Step 2 involves using the kobopatch system. If this is more than you want to have to deal with then you can probably get away with just steps 1 & 3, but only if you're prepared to read your book with the [Aa] font setting set to 'Publisher Default'.

[PenguinCEO]

Originally Posted by jackie_w

The answer is 'yes' but whether the effort involved in the solution will be acceptable to you is another matter. The solution is different depending on whether you are going to read the book as a kepub or a standard epub on your Kobo.

You mentioned kepub above so steps 1-3 in this post should give you some pointers.

Step 2 involves using the kobopatch system. If this is more than you want to have to deal with then you can probably get away with just steps 1 & 3, but only if you're prepared to read your book with the [Aa] font setting set to 'Publisher Default'.

The problem is not the effort. The problem is that

font-family: monospace;

is standard CSS, and if kobo doesn't recognize that directive it has to be considered a bug. Sideloading external fonts and patching up the firmware is not a solution as far as setting a standard directive into an epub means to make a not-portable ebook.

[Quoth]

epub format monospace seems ok on apps, Sony, Nook, Binatone and Kobo. Only Kobo uses kepub?

[jackie_w]

Originally Posted by PenguinCEO

The problem is not the effort. The problem is that

font-family: monospace;

is standard CSS, and if kobo doesn't recognize that directive it has to be considered a bug. Sideloading external fonts and patching up the firmware is not a solution as far as setting a standard directive into an epub means to make a not-portable ebook.

My mistake. I thought you were looking for a kepub solution rather than wanting to debate what constitutes a "bug".

For whatever reason, Kobo have decided not to include a built-in monospace font and workarounds are the only solution currently available for kepubs. If you really want to limit yourself to 'standards' then embed your monospace font and restrict yourself to using 'Publisher Default'.

I'm sorry I wasted my time trying to help you.

[PenguinCEO]

Originally Posted by jackie_w

My mistake ...

You didn't understand what I said. So, yes, you did a mistake.

[JSWolf]

Why is it that Kobo hasn't fixed the monospace bug in RMSDK?

[MGlitch]

Originally Posted by JSWolf

Why is it that Kobo hasn't fixed the monospace bug in RMSDK?

I'd wager it's the same reason other things people here have complained about are still the way they are

Not enough people complain to Kobo about the issue.

[djazz]

Kobo doesn't have a monospace font. Embed one in the ebook.

[DNSB]

Originally Posted by PenguinCEO

The problem is not the effort. The problem is that

font-family: monospace;

is standard CSS, and if kobo doesn't recognize that directive it has to be considered a bug. Sideloading external fonts and patching up the firmware is not a solution as far as setting a standard directive into an epub means to make a not-portable ebook.

Hmm... looking at the xhtml code tag: "The code tag is designed to display computer code in a special font, usually in a mono spaced font style. However, the exact appearance will be browser dependent. You may still need to use various HTML tags, such as br and p, to create a presentation and appearance to suit your needs."

To quote: "reading systems are not required to provide the fonts necessary to display every unicode character, though they are required to display at least a placeholder for characters that cannot be displayed fully" (Open Publication Structure 2.0.1).

So are we confusing "usually" with "must"? Or requiring a reading system to support all fonts? Neither of these is required so where does the "bug" come in.

If you are truly worred about sideloading or patching, then embed the monospaced font in your ebook. Though I fail to see how patching the software on your Kobo makes a non-portable ebook -- you haven't modified the ebook.

[DNSB]

Originally Posted by JSWolf

Why is it that Kobo hasn't fixed the monospace bug in RMSDK?

What monospace bug in RMSDK? RMSDK will happily display a monospaced font if one is available on the device.

[PenguinCEO]

Originally Posted by DNSB

However, the exact appearance will be browser dependent.

Where browsers and unicode come out? The object of this thread is completely different.

[PenguinCEO]

.....

[JSWolf]

Originally Posted by DNSB

What monospace bug in RMSDK? RMSDK will happily display a monospaced font if one is available on the device.

Every other version RMSDK I've seen works with a monospace font. That includes ADE for Windows, OS X, Sony Readers, and nook. Kobo is the only one with monospace not working.