Firmware 4.19.14123 release

[geek1011]

Patches for 4.19.14123 are out.

Note: Please discuss these patches in the linked thread.

[JSWolf]

I did find a fix in this new firmware. The header/footer for ePub has been fixed so that the time remaining now works.

[lkmiller]

Fix for an auto/sleep sync issue that drained battery.

This will be nice to see. I've woken up to a drained battery a couple times when I left wi-fi on overnight. I prefer to leave it on.

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

[Semwize]

Originally Posted by jackie_w

but the changed choice of dictionary doesn't 'stick' for when I lookup the next word

I have like works (if selecting for example dicthtml-n3, then the next word searching for in offense).

The language in ereader is NOT English.

ETA: Jackie, tried on another ereader, yes, there is this error.

I closed the book on the first ereader, opened it and looked - this error appeared. Really - does not remember. The last dictionary is displayed - which was used before exiting the book being read.

[jackie_w]

Originally Posted by Semwize

I have like works (if selecting for example dicthtml-n3, then the next word searching for in offense).

The language in ereader is NOT English.

ETA: Jackie, tried on another ereader, yes, there is this error.

I closed the book on the first ereader, opened it and looked - this error appeared. Really - does not remember. The last dictionary is displayed - which was used before exiting the book being read.

Ah, yes, well-spotted. The 'last dictionary used' is remembered when you close the book and is then the new default dictionary for that book on subsequent openings.

[davidfor]

A discussion about the change for monospace fonts started in the patch thread that really should be here...

Originally Posted by snarkophilus

I'm hitting the same thing. Updated with new 4.19.14123 firmware, installed a few patches with kobopatch. I've installed the Courier Prime fonts in the /Fonts directory on my Kobo and restarted. They are the only fonts with "Courier" in their name, and the firmware is seeing them in that I can switch the whole book to Courier Prime.

I've got a book that has this css:

p.extra_hanging_indent {
  font-size: 0.9em;
  margin-top: 0;
  text-indent: -1em;
  padding-left: 2em;
  font-family: "Courier New", monospace;
}

but text with that CSS selector is showing up with the default book font. The rest of that CSS chunk is working. That text does show as a monospace font with Sigil and the Calibre book viewer.

This is on a Kobo Aura 2 (1st edition) if that matters.

Feeling like I'm missing something very basic here. Any suggestions?

(Note: Should I have posted here where there's a monospace discussion going on, or on the main Firmware 4.19.14123 release thread? Happy to move this question there.)

I don't have the device I tested this on with me. But, I did have a different test book with some monospace in it. I don't remember which font I used before, but "Courier Prime" worked. The book has the code:

    <p class="header" id="ue365c97c-d51a-42b7-be0b-faa3bc4bb251"><span class="generic-monospace">Monospace generic font family (forced/fallback)</span></p>

Plus several similar lines. In the stylesheet is:

.generic-monospace{font-family:monospace;}

It worked when I added font name that wasn't on the device as well as the "monospace".

The book was one posted here a while ago with the title "Simple Generic Font Family Test (and fall back Test) for epub". I have attached to save the trouble of searching for it.

[snarkophilus]

Originally Posted by davidfor

A discussion about the change for monospace fonts started in the patch thread that really should be here...

Thanks David.

I don't have the device I tested this on with me. But, I did have a different test book with some monospace in it. I don't remember which font I used before, but "Courier Prime" worked.

[ ... ]

The book was one posted here a while ago with the title "Simple Generic Font Family Test (and fall back Test) for epub". I have attached to save the trouble of searching for it.

When I open that test book on my Kobo and go to the monospace section, the heading and all four styles (regular, italic, bold, bold italic) appear to be in a bold italic monospace font. Note I say "appear", because looking at the Courier Prime font with Windows' font viewer shows the regular style is a dark/think font anyway.

The rest of your test epub seems to work as expected. The serif, cursive and fantasy sections all use the standard font (either my preferred Bookerly or the Publisher Default font), and sans-serif section uses a sans-serif font.

Does that help pin-point the problem?

I'll experiment with removing the "Courier New" out of the CSS in this book, but longer term it'd be nice if I didn't have to tweak the CSS for a monospace font to work.

[davidfor]

Originally Posted by snarkophilus

When I open that test book on my Kobo and go to the monospace section, the heading and all four styles (regular, italic, bold, bold italic) appear to be in a bold italic monospace font. Note I say "appear", because looking at the Courier Prime font with Windows' font viewer shows the regular style is a dark/think font anyway.

The rest of your test epub seems to work as expected. The serif, cursive and fantasy sections all use the standard font (either my preferred Bookerly or the Publisher Default font), and sans-serif section uses a sans-serif font.

Does that help pin-point the problem?

I'll experiment with removing the "Courier New" out of the CSS in this book, but longer term it'd be nice if I didn't have to tweak the CSS for a monospace font to work.

Attached is a screenshot from my Clara HD. This is with the font set the "Publisher default". The different lines all look like what I expect they should. This is with the style for monospace test as:

.generic-monospace{font-family:"Courier New", monospace;}

I added the "Courier New" earlier and forgot to take it out.

The monospace font I am using is "Courier Prime" from the first link I found when searching earlier today. The file names in the "fonts" directory are:

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

I don't have any other sideloaded fonts, and I don't use any patches or other hacks.

When I tested this before it was on my Aura ONE. I'll recheck that as I think I used a different Courier font. I think the only difference is that I used the single letter for the type of font.

[snarkophilus]

I'm making progress but getting a little more confused along the way!

Step one - remove all patches, revert to stock firmware, and only side loaded font is Courier Prime. The files in my /fonts directory on the Kobo are:

NUC 6163> ls -l fonts
total 376
-rw-r--r-- 1 simon simon 91908 Jan 19  2013 Courier Prime Bold Italic.ttf
-rw-r--r-- 1 simon simon 91368 Jan 19  2013 Courier Prime Bold.ttf
-rw-r--r-- 1 simon simon 96196 Jan 19  2013 Courier Prime Italic.ttf
-rw-r--r-- 1 simon simon 98156 Jan 19  2013 Courier Prime.ttf

Your test epub with this is the attached screen_017.png. This is the "every style appears as bold italic" problem. I've confirmed that with Windows Font Viewer that each of these font files does contain the style that the name says.


Step two - toss out Courier Prime and copy Courier New from my PC to the /fonts directory. Progress! screen_020.png attached shows a nice monospace font, yay.


Now for the confusion.

screen_021.png is with font-family: monospace; in my book's CSS. This is clearly a sans-serif config (?!?!).

screen_022.png is with font-family: "Courier New", monospace; in my book's CSS. YAY !!!!!


Two takeouts so far then:
1- I guess the Courier Prime I found was a dud? Or at least a partial dud since Windows seemed happy but the Kobo obviously wasn't.
2- I'm still having problems with a plain font-family: monospace; but have something that works with "Courier New" added explicity. I'd like to avoid that, but I'm still a long way ahead of where I was when I started.

Tomorrow I'll re-install the kobopatches and see if Courier New still works.

EDIT: Well dang. If I choose Bookerly as my font instead of Publisher Default, then my monospace text reverts to Bookerly as well... Still not there yet.

[rtiangha]

Originally Posted by snarkophilus

Your test epub with this is the attached screen_017.png. This is the "every style appears as bold italic" problem. I've confirmed that with Windows Font Viewer that each of these font files does contain the style that the name says.

As for the bold-italic problem, it isn't enough for just the names to match; the weight of the font needs to be consistent between the PS Name, OS/2 and PANOSE tables as well. That's why some people strip all the PANOSE data out as usually that's where most fonts that have issues have the wrong weight set. I believe the issue with stock Courier Prime is that the PANOSE weights are set to thin for all four variants, when they really should be set to either Book or Bold depending on the type and Kobo is picky about stuff like that.

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.

[davidfor]

Originally Posted by snarkophilus

I'm making progress but getting a little more confused along the way!

Step one - remove all patches, revert to stock firmware, and only side loaded font is Courier Prime. The files in my /fonts directory on the Kobo are:

NUC 6163> ls -l fonts
total 376
-rw-r--r-- 1 simon simon 91908 Jan 19  2013 Courier Prime Bold Italic.ttf
-rw-r--r-- 1 simon simon 91368 Jan 19  2013 Courier Prime Bold.ttf
-rw-r--r-- 1 simon simon 96196 Jan 19  2013 Courier Prime Italic.ttf
-rw-r--r-- 1 simon simon 98156 Jan 19  2013 Courier Prime.ttf

Your test epub with this is the attached screen_017.png. This is the "every style appears as bold italic" problem. I've confirmed that with Windows Font Viewer that each of these font files does contain the style that the name says.

The problem is the file names. The different styles have specific names based on the main file. Because they are wrong, the firmware is taking the first font file it can find that starts with "Courier". That just happens to be "Courier Prime Bold Italic.ttf". Then, as it cannot find the the other styles for it, this is used for all styles.

Look at my post and match that. See the font thread in the stickies for more details.

EDIT: Well dang. If I choose Bookerly as my font instead of Publisher Default, then my monospace text reverts to Bookerly as well... Still not there yet.

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

[JSWolf]

Originally Posted by snarkophilus

I'm making progress but getting a little more confused along the way!

Remove Bookerly and remove any monospace fonts. 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.

[JSWolf]

Originally Posted by rtiangha

As for the bold-italic problem, it isn't enough for just the names to match; the weight of the font needs to be consistent between the PS Name, OS/2 and PANOSE tables as well. That's why some people strip all the PANOSE data out as usually that's where most fonts that have issues have the wrong weight set. I believe the issue with stock Courier Prime is that the PANOSE weights are set to thin for all four variants, when they really should be set to either Book or Bold depending on the type and Kobo is picky about stuff like that.

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.

Just a quick note. This is a different version of Courier Prime then the one from Google Fonts. Also, in the patch thread, someone else used the Google version of Courier Prime and it worked.

[icallaci]

Originally Posted by snarkophilus

I'm making progress but getting a little more confused along the way!

-rw-r--r-- 1 simon simon 91908 Jan 19 2013 Courier Prime Bold Italic.ttf
-rw-r--r-- 1 simon simon 91368 Jan 19 2013 Courier Prime Bold.ttf
-rw-r--r-- 1 simon simon 96196 Jan 19 2013 Courier Prime Italic.ttf
-rw-r--r-- 1 simon simon 98156 Jan 19 2013 Courier Prime.ttf

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.