Firmware 4.19.14123 release

[Calenorn]

Originally Posted by jackie_w

Can anyone else confirm this about fw 4.19 ...

If I lookup a word in the dictionary then choose a dictionary which isn't just 'English', the lookup works fine, but the changed choice of dictionary doesn't 'stick' for when I lookup the next word. This used to work OK in fw 4.18.

I tried it on an unpatched H2O in case my heavy use of patches was muddying the waters. The results were the same.

Yes. It does this on my unpatched Clara. The dictionary always opens to 'English' no matter what I used previously. Requires annoying extra clicks.

[jackie_w]

@snarkophilus,

Welcome to the world of font wrangling on Kobos. I seem to remember both of us were active on similar threads in the Sony days.

I'm a bit lost in the maze of your findings so far but here are a couple of old links which might have relevant info now or in the future.

• Getting monospace to work in kepubs
  
• Even if you're reading standard epubs rather than kepubs you may still be butting heads with the fact that the default epub override CSS inside the firmware contains:
  

  body, p { font-family: -ua-default !important; }

  which has the effect of ignoring any font-family styles set at the <p> tag level, in favour of your font-of-choice. For those who want it, there's a kobopatch ('Un-force font-family override p tags (std epubs)' to replace the body, p with a simple body.
• The general bold/italic problem with sideloaded fonts on Kobo, as already mentioned by @rtiangha. Posts #2 and #9 in this thread have detailed instructions on fixing the panose issue.

[JSWolf]

The font names should be...

Courier Prime-Regular.ttf
Courier Prime-Bold.ttf
Courier Prime-Italic.ttf
Courier Prime-BoldItalic.ttf

as long as the internal font name is Courier Prime.

[dmapr]

Originally Posted by JSWolf

The font names should be...

Courier Prime-Regular.ttf
Courier Prime-Bold.ttf
Courier Prime-Italic.ttf
Courier Prime-BoldItalic.ttf

as long as the internal font name is Courier Prime.

Not to be too pedantic, but the regular flavor can be named just Courier Prime.ttf. -Regular suffix is optional, but the others are not.

[JSWolf]

Originally Posted by dmapr

Not to be too pedantic, but the regular flavor can be named just Courier Prime.ttf. -Regular suffix is optional, but the others are not.

That's true. Thanks for pointing that out.

[DNSB]

Originally Posted by dmapr

Not to be too pedantic, but the regular flavor can be named just Courier Prime.ttf. -Regular suffix is optional, but the others are not.

True. You can also use 1 letter abbreviations. I prefer using the 4 longer names for consistency.

[dmapr]

Originally Posted by DNSB

True. You can also use 1 letter abbreviations. I prefer using the 4 longer names for consistency.

You're right, I completely forgot about those. Somehow Z for BoldItalic never sat well with me. And if I'm not mistaken the abbreviations don't need the dash, right?

font.ttf is the same as font-Regular.ttf
fontb.ttf is the same as font-Bold.ttf
fonti.ttf is the same as font-Italic.ttf
fontz.ttf is the same as font-BoldItalic.ttf

[rcentros]

Deleted

[JSWolf]

Originally Posted by dmapr

You're right, I completely forgot about those. Somehow Z for BoldItalic never sat well with me. And if I'm not mistaken the abbreviations don't need the dash, right?

font.ttf is the same as font-Regular.ttf
fontb.ttf is the same as font-Bold.ttf
fonti.ttf is the same as font-Italic.ttf
fontz.ttf is the same as font-BoldItalic.ttf

IMHO, it's easier to just use the longform font filenames. It's easier to know which font it is just by looking.

[snarkophilus]

Originally Posted by rtiangha

If you're looking for a Courier font that's optimized for Kobo, why not check out GeoffR's modified version of Courier Prime? He corrected the PANOSE weights and made a few other tweaks.

Originally Posted by davidfor

The problem is the file names.
[ ... ]
Look at my post and match that. See the font thread in the stickies for more details.

Originally Posted by icallaci

Are you sure your font names use spaces between every word? The Courier Prime fonts I downloaded have hyphens in them, like this: Courier Prime-Bold.ttf, Courier Prime-Italic.ttf, Courier Prime-BoldItalic.ttf, etc.

Originally Posted by JSWolf

Download Courier Prime from Google at https://fonts.google.com/specimen/Co...=Courier+Prime and install that in fonts. Reboot and see what happens. Also, make sure that Courier Prime shows in the font list.

So all of the above now work for the test epub, for both using "Publisher Default" as the font or using my sideloaded Bookerly. GeoffR's modified font, the font downloaded from the link Jon posted (once I actually found the download section!), and renaming the Courier Prime files I first downloaded from the official (?) Quote-Unquote Apps site to include a '-' instead of a space before the weight/style suffixes all worked. Yay for that!

The moral of the story so far - make sure you either download a monospace font where the files are named correctly or fix the file names if they are dodgy.

Originally Posted by davidfor

If you choose a specific, all the fonts specified in the book are overridden. The "Publisher Default" will respect the fonts in the book.

Aha, that makes sense (now). Which takes me to ...

Originally Posted by jackie_w

Welcome to the world of font wrangling on Kobos. I seem to remember both of us were active on similar threads in the Sony days.

Indeed! Almost come full circle with fonts and devices

I'm a bit lost in the maze of your findings so far but here are a couple of old links which might have relevant info now or in the future.

• Getting monospace to work in kepubs
  
• Even if you're reading standard epubs rather than kepubs you may still be butting heads with the fact that the default epub override CSS inside the firmware contains:
  

  body, p { font-family: -ua-default !important; }

  which has the effect of ignoring any font-family styles set at the <p> tag level, in favour of your font-of-choice. For those who want it, there's a kobopatch ('Un-force font-family override p tags (std epubs)' to replace the body, p with a simple body.
• The general bold/italic problem with sideloaded fonts on Kobo, as already mentioned by @rtiangha. Posts #2 and #9 in this thread have detailed instructions on fixing the panose issue.

The book I have with the monospace font is a kepub. For now I've got GeoffR's modified Courier Prime font sideloaded, as well as Bookerly.

With the font set to either "Publisher Default" or Bookerly, even with the 'Un-Force user font-family in KePubs' patch applied, the only way I can get the book to display Courier GR is to have font-family: "Courier GR", monospace; in my CSS (guessing the ", monospace" isn't doing much here). Curiously, if I just use font-family: monospace; I see a sans-serif font instead of a monospace font for any text that is meant to be monospace (!?!).

From reading the post you linked to, I think I've done option 2 and that isn't working. Option 3 is working, but is the case I'm trying to avoid (needing to modify every epub).

Jackie - do you have just font-family: monospace; working for kepubs when using a side-loaded font as your chosen font (instead of "Publisher Default") with the current kobo firmware?

Originally Posted by davidfor

Bug fixes that I know of:

• Path for monospace font changed to match other fonts and name is "Courier". This should mean that any correctly sideloaded font whose name starts with "Courier" will be used when the monospace font face is specified.

David - do you know if this was an epub only fix, or a fix for kepub too?

[davidfor]

Originally Posted by snarkophilus

David - do you know if this was an epub only fix, or a fix for kepub too?

The change is in the RMSDK. That is for epubs only. I don't believe there is any change for kepubs. I should have put that in my post.

[jackie_w]

Originally Posted by snarkophilus

The book I have with the monospace font is a kepub. For now I've got GeoffR's modified Courier Prime font sideloaded, as well as Bookerly.

With the font set to either "Publisher Default" or Bookerly, even with the 'Un-Force user font-family in KePubs' patch applied, the only way I can get the book to display Courier GR is to have font-family: "Courier GR", monospace; in my CSS (guessing the ", monospace" isn't doing much here). Curiously, if I just use font-family: monospace; I see a sans-serif font instead of a monospace font for any text that is meant to be monospace (!?!).

From reading the post you linked to, I think I've done option 2 and that isn't working. Option 3 is working, but is the case I'm trying to avoid (needing to modify every epub).

Jackie - do you have just font-family: monospace; working for kepubs when using a side-loaded font as your chosen font (instead of "Publisher Default") with the current kobo firmware?

There's some confusion here, I think. The 3 items in my 'Getting monospace to work in kepubs' link are not options, they're steps, i.e. you have to do all 3 to see monospace in kepubs.

If your book's CSS contains:

font-family: "Courier GR", monospace;

then the Kobo will respond to:
- the monospace value if you send-to-device as epub
- the "Courier GR" value if you send-to-device as kepub.

This is, indeed, a PITA for kepubs. It's unfortunate, but normal, behaviour. I also don't want to hard-code font-family names in my calibre library's master copy of the epub, especially if I want to change the mono font to something else later on.

My personal workaround for avoiding having to manually edit every epub individually was to hack my copy of the KoboTouchExtended plugin so that all occurrences of font-family:monospace; in a CSS file are auto-corrected to my mono-fontname-of-choice when sending kepubs via the calibre send-to-device. Whether this is a practical solution depends on where you're at with your new project of 'let's learn about calibre plugins'. [Hacking KTE to indulge your latest "bright ideas" can be quite addictive - but that's a story unsuited to this thread.]

BTW, kepubs displaying font-family:monospace; as sans-serif as default is also unfortunate, but normal, behaviour. It's been this way as long as I can remember.

Now that Kobo have made some effort, in 4.19, to improve the monospace situation for standard epubs, it's anyone's guess whether they'll do something for kepub in the near future. I'll believe it when I see it, but we live in hope.

[icallaci]

Originally Posted by snarkophilus

Aha, that makes sense (now). Which takes me to ...

David - do you know if this was an epub only fix, or a fix for kepub too?

I misspoke in my earlier post when I said it was working for kepubs too. I reloaded a book as a kepub, and when I opened it on my Kobo, it displayed monspace fonts. BUT...it turns out I had two different drivers enabled, so I had BOTH a kepub and an epub of the same book on my reader. My Kobo was opening the epub one. So, long story short, the monspace fix is only for epubs, not kepubs. Too bad. I hope Kobo fixes that.

[snarkophilus]

Originally Posted by davidfor

The change is in the RMSDK. That is for epubs only. I don't believe there is any change for kepubs. I should have put that in my post.

Good, that now makes sense. Who do we lobby for the kepub fix?

[snarkophilus]

Originally Posted by jackie_w

There's some confusion here, I think. The 3 items in my 'Getting monospace to work in kepubs' link are not options, they're steps, i.e. you have to do all 3 to see monospace in kepubs.

If your book's CSS contains:

font-family: "Courier GR", monospace;

then the Kobo will respond to:
- the monospace value if you send-to-device as epub
- the "Courier GR" value if you send-to-device as kepub.

[ding sound]The lightbulb goes on! In hindsight I'm not sure how I worked out that items 2 and 3 were a sequnce and not options, given that item 1 was always necessary. This all makes sense now.

This is, indeed, a PITA for kepubs. It's unfortunate, but normal, behaviour. I also don't want to hard-code font-family names in my calibre library's master copy of the epub, especially if I want to change the mono font to something else later on.

Yes, I'm also very much interested in not having to embed my current favourite monospace font name in case that changes in the future too. Also it's just not "clean" .

My personal workaround for avoiding having to manually edit every epub individually was to hack my copy of the KoboTouchExtended plugin so that all occurrences of font-family:monospace; in a CSS file are auto-corrected to my mono-fontname-of-choice when sending kepubs via the calibre send-to-device. Whether this is a practical solution depends on where you're at with your new project of 'let's learn about calibre plugins'. [Hacking KTE to indulge your latest "bright ideas" can be quite addictive - but that's a story unsuited to this thread.]

My first look out your "get old books" plugin very much confounded me. I've had a little success with tinkering with the Count Pages plugin but that was isloated to a small section of code. I had a quick look inside the KTE plugin and can see no obvious place to even start with inspecting/modifying all CSS files. Did you create something like a css_names() based on the existing html_names() and then loop over those files with a search/replace?

For a slightly different approach, is there a way of mixing these @font-face definitions and the
Modify CSS option in the KOBOTOUCH driver so that a reference to font-family: monospace; will do what I want?

BTW, kepubs displaying font-family:monospace; as sans-serif as default is also unfortunate, but normal, behaviour. It's been this way as long as I can remember.

That's a very interesting definition of "normal" then !!!

I'll believe it when I see it, but we live in hope.

I shall join you in living in hope...