Kobalt: an alternative reader app for Kobo devices

[JSWolf]

Originally Posted by DNSB

What if I am reading a French language book? Or one of those many books where the chapter name is simply a number? There is no standard way of naming a chapter.

In theory, you could do this for an ePub3 book that made the correct use of epub:type (epub:type="appendix" for example) or ARIA roles but those books are currently not all that common though accessibility should make them more common.

See EPUB Type to ARIA Role Authoring Guide for more on the ARIA roles and epub:type to role conversion.

I've seen chapter's named with a title and no number or the word chapter.

[MrSilverstrike]

Originally Posted by fogice

I believe that I did that the second time. Epub directly copied into Kobo directory system. Epub airdropped to iPhone/Readest. Would either of those methods alter the file? Is there another transfer method that would work better? (If I get this step working, I plan to set up a Calibre web instance that I can access with Tailscale in order to move books ad hoc to iPhone/Readest.)

(edit) just saw the other edit. I'll wait.

That being said, any info you have about the mismatch, the epub file etc may be useful to try to reproduce the issue. If you can mail me more details, please consider doing so. I definitely would like to reproduce what you're running into and potentially fix it (or tell you what to fix).

[Uncle Robin]

Originally Posted by MrSilverstrike

Exactly as the posts above say: there's no standard for this, so no. Not possible, at least not on a low-power device such as this. It'd take training a neural net and stuff like that if you realistically wanted to do this.

Programmatically, it'd be guesswork at best, and doing this for the many languages that are out there is essentially not something I'm interested in.

What about an option to set it manually, as in KOReader?

There when you choose Custom page flows and go into to the page browser, you mark the end of the reading material and the page count is adjusted accordingly, as in the images attached

[fogice]

Originally Posted by MrSilverstrike

That being said, any info you have about the mismatch, the epub file etc may be useful to try to reproduce the issue. If you can mail me more details, please consider doing so. I definitely would like to reproduce what you're running into and potentially fix it (or tell you what to fix).

I've said everything that I can think of. I'll wait for the next full beta (or nightly) since you said it might fix things, and reach out again after that if I'm still having issues.

[MrSilverstrike]

Originally Posted by Uncle Robin

What about an option to set it manually, as in KOReader?

There when you choose Custom page flows and go into to the page browser, you mark the end of the reading material and the page count is adjusted accordingly, as in the images attached

That's definitely possible, then. This is definitely something I'd consider a nice-to-have feature, so it's not something I'll likely add right away -- after v1.0.

[Uncle Robin]

Originally Posted by MrSilverstrike

That's definitely possible, then. This is definitely something I'd consider a nice-to-have feature, so it's not something I'll likely add right away -- after v1.0.

Oh absolutely. I was really just replying the context of the other person's request. For me, there's absolutely no rush at all

version 1.01 would be fine

[JSWolf]

Originally Posted by Uncle Robin

What about an option to set it manually, as in KOReader?

There when you choose Custom page flows and go into to the page browser, you mark the end of the reading material and the page count is adjusted accordingly, as in the images attached

IMHO, that's bloat. I'd rather not have bloat and use the space for real features.

[Sirtel]

Heh. At this rate, soon there won't be any difference between Kobalt and KOReader...

[Uncle Robin]

Originally Posted by Sirtel

Heh. At this rate, soon there won't be any difference between Kobalt and KOReader...

I'm looking forward to trying Kobalt out when it gets to 1.0 - the 'exclude end matter' feature is useful for those who read a lot of non-fiction, for sure.

[Dal Bhat]

You may want to wait until beta 6 to try again

I see that you've completed 21/21 tracking issues. Is 6 coming soon?

[howyoudoin]

Originally Posted by JSWolf

IMHO, that's bloat. I'd rather not have bloat and use the space for real features.

Including end of book extras in the page/time/percentage counts is the real bloat!!

[MrSilverstrike]

Originally Posted by Dal Bhat

I see that you've completed 21/21 tracking issues. Is 6 coming soon?

Soon, yes. Some bugs came up during a validation run, fixing those first.

[Acopdegarrotix]

When I change the size of the text, the line height inside a table is not scaled accordingly.

body{margin:0;padding:0;font-size:1em;}
th, td{vertical-align:top;}
.tiny{font-size:0.8em;}
.huge{font-size:1.2em;}

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops">
<head>
  <title></title>
  <link href="../Styles/Style0001.css" type="text/css" rel="stylesheet"/>
</head>

<body>
  <p>Font-size: 1em - Lorem ipsum</p>

  <blockquote class="tiny">
    <p>Font-size: 0.8em - Donec tellus augue,</p>
  </blockquote>

  <table class="tiny">
    <thead>
      <tr>
        <th>Lorem</th>
        <th>Ipsum</th>
      </tr>
    </thead>

    <tbody>
      <tr>
        <td>Font-size: 0.8em -</td>
        <td>Donec metus ligula,</td>
      </tr>
    </tbody>
  </table>

  <p class="tiny">Font-size: 0.8em - Donec</p>
</body>
</html>

The samples I've attached are ePub 3, but the issue occurs also in ePub 2.

Thank you very much for your efforts, they are greatly appreciated.

[MrSilverstrike]

Originally Posted by Acopdegarrotix

When I change the size of the text, the line height inside a table is not scaled accordingly.

Thanks for reporting, this will be fixed in beta 6 which will release soon!

[Acopdegarrotix]

Brilliant!