Firmware 3.15 discussion thread - Page 13

Jakkal · 05-08-2015, 05:28 AM

The update is available in Germany now. I have updated my Aura and Aura HD and so far I like it, no issues at all. The only thing I don't like is the missing chess.

BTW The Aura updates twice as fast as the Aura HD.

Nick_1964 · 05-08-2015, 05:37 AM

Quote:

Originally Posted by Jakkal

The update is available in Germany now. I have updated my Aura and Aura HD and so far I like it, no issues at all. The only thing I don't like is the missing chess.

BTW The Aura updates twice as fast as the Aura HD.

I can understand that you miss the chess, but on the other hand, it is an e-reader, by leaving things they can lower the amount space that the firmware need and there will be more space for books !

rcentros · 05-08-2015, 07:50 AM

Quote:

Originally Posted by Nick_1964

I can understand that you miss the chess, but on the other hand, it is an e-reader, by leaving things they can lower the amount space that the firmware need and there will be more space for books !

Except Chess is still there -- they just took away the link. I know this because -- sometime in the last couple of days -- my Kobo Glo updated to 3.15.0. Since I had Chess as one of the shortcuts on my front page, I can still go to it and play it. But I can't get to it via Beta anymore.

But now I've got a new problem. My two added fonts (Miller and Constantia) are now italic. Is there a way to fix them? The other fonts (built-in) fonts seem to be okay.

s4nder · 05-10-2015, 04:55 AM

Kobo Nickel still has huge line spacing. I wonder when that'll get fixed, I generally like the font.

GERGE · 05-10-2015, 05:23 AM

I don't think Kobo Nockel is a good text typeface. Too small x-heights.

Joques · 05-10-2015, 08:23 AM

S4nder, I absolutely agree. I especially like it for reading fantasy fiction.

jackie_w · 05-10-2015, 09:02 AM

Quote:

Originally Posted by rcentros

My two added fonts (Miller and Constantia) are now italic. Is there a way to fix them?

Is it possible you have a problem with your font filenames? Kobos are very strict about sideloaded font names.

My Constantia files are named
Constantia-Regular.ttf (Constantia.ttf should also be OK)
Constantia-Italic.ttf
Constantia-Bold.ttf
Constantia-BoldItalic.ttf

In addition, the red part must match exactly the internal font name.

I don't use them but I have a set of Miller font files. The internal font name is Miller Text so I'd expect the external files to be named
Miller Text-Regular.ttf (Miller Text.ttf should also be OK)
Miller Text-Italic.ttf
Miller Text-Bold.ttf
Miller Text-BoldItalic.ttf

If this does turn out to be the problem don't forget to do a full power off/on reboot cycle to get the newly named fonts properly integrated.

GERGE · 05-10-2015, 09:42 AM

Kobo checks both file name and metadata. They must both be properly done. I am using TransType 4 for editing metadata but you check them with free FontForge.

By the way, objectively speaking Kobo Nickel is a bad text typeface. Spacing between letters is too big and x-height is too small. I don't know who designed it for Kobo but it really isn't good. I am not saying that it is unreadeable, but this is not how a text type should be.

dclauzel · 05-10-2015, 11:48 AM

I just did get the update to 3.15.0 (d60578c5e1, 27/04/2015) on my Aura HD (French language, Kobo affiliate), and the chess are still here.

The entry for chess did indeed disappeared from the beta features, but the launching tile is still present on my start screen (from a previous session). I can still run it without any difference.

So yes, we can still play chess; the trick is to be able to launch it. The only way I can find is by having the tile on the start screen.

dordale · 05-10-2015, 11:49 AM

Quote:

Originally Posted by s4nder

Kobo Nickel still has huge line spacing. I wonder when that'll get fixed, I generally like the font.

Just curious--I've only used Kobos since Firmware version 3.11 (or there abouts). In the firmware versions I've used, Kobo Nickel has always had huge line spacing. If it weren't for that, I think I'd like the font. Has Kobo Nickel always had the huge line spacing issue--or in earlier firmware versions was the spacing more reasonable? Is there any hope that Kobo will reduce the line spacing in a future firmware?

Namenlos · 05-10-2015, 11:52 AM

Quote:

Originally Posted by Namenlos

Has anyone tested this on the Kobo Mini? I don't have a µsd cardreader right now, so I don't want to try it out without a confirmation.

Anyone? I am currently on 3.11

rcentros · 05-10-2015, 05:09 PM

Quote:

Originally Posted by jackie_w

Is it possible you have a problem with your font filenames? Kobos are very strict about sideloaded font names.

That's what it turned out to be -- although, oddly, the old names worked fine in 3.12.x and 3.13.x? I figured this out by experimentation when I noted that the Kobo version of the font worked, both regular and italic (although it was too light and, since my Glo is not jailbroken, I couldn't adjust weight). The Kindle version of the font won't change weight either -- but it's at the darkness I want, as is. The name of the Kindle font was (something like) Serif_Regular and Serif_Italic (nothing about Constantia) -- so, until I changed the name, Italic came first -- I would get everything in Italic. When I renamed the fonts something like Serif_a_Regular and Serif_b_Italic, I would get the regular font, but -- again -- for everything. When I changed the names to match the Kobo font's name scheme, that's when it worked (Constantia-Regular and Constantia-Italic, I believe). I'm guessing now I could add the bold fonts, if I wanted them (even in 3.12.x and 3.13.x the Kobo would default to bold unless I left out the bold versions of the font).

But all this was just -- basically -- blind luck for me. Now that I know how the naming scheme works I should be able to add more fonts without having to experiment each time.

Thanks for the explanation. I've clipped your message for future reference.

rcentros · 05-10-2015, 05:10 PM

Quote:

Originally Posted by dclauzel

So yes, we can still play chess; the trick is to be able to launch it. The only way I can find is by having the tile on the start screen.

Will that launching tile disappear over time, if you don't use Chess?

93terp · 05-10-2015, 08:54 PM

With 3.15 installed on both my GloHD & H2O, and both units patched, page turns seem much snappier on the GloHD.

Maybe I missed it somewhere but I didn't see mention of a new 4th screen layout option with 3.15. I don't have either reader in front of me but IIRC the layout is more "vertical" in nature, with page turns on the top & bottom sections of the screen.

sparklemotion · 05-10-2015, 09:02 PM

Quote:

Originally Posted by mathil

I updated my H2O a couple of days ago from 3.13.1, after a factory reset. I almost exclusively read sideloaded kepubs, haven't tested it with anything else so far but I'm pretty happy with this update. The interface is snappier, highlighting is faster and more precise, book processing time has been reduced.

Wow, I just noticed how much faster highlighting is with this update. Very nice!

05-10-2015, 11:48 AM	#189
dclauzel Enthusiast Posts: 47 Karma: 11516 Join Date: Sep 2013 Location: France Device: Kobo Aura HD	Chess still here, but… I just did get the update to 3.15.0 (d60578c5e1, 27/04/2015) on my Aura HD (French language, Kobo affiliate), and the chess are still here. The entry for chess did indeed disappeared from the beta features, but the launching tile is still present on my start screen (from a previous session). I can still run it without any difference. So yes, we can still play chess; the trick is to be able to launch it. The only way I can find is by having the tile on the start screen.

05-10-2015, 08:54 PM	#194
93terp Fear The Turtle! Posts: 868 Karma: 4067244 Join Date: Sep 2009 Location: Margaritaville Device: KV, Kobo Forma, Kobo A1LE, KO3, K3	Page Turns - GloHD & H2O With 3.15 installed on both my GloHD & H2O, and both units patched, page turns seem much snappier on the GloHD. Maybe I missed it somewhere but I didn't see mention of a new 4th screen layout option with 3.15. I don't have either reader in front of me but IIRC the layout is more "vertical" in nature, with page turns on the top & bottom sections of the screen.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
MobileRead Discussion/Suggestion Thread	WT Sharpe	Book Clubs	378	11-16-2017 08:25 PM
Hugo 2014 Discussion Thread	Pete731	General Discussions	107	08-23-2014 06:55 AM
Wicked discussion thread.	WT Sharpe	Reading Recommendations	15	08-07-2011 08:11 AM
iLiad FBShot discussion thread	scotty1024	iRex Developer's Corner	2	11-16-2006 05:30 PM

05-08-2015, 05:28 AM	#181
Jakkal Member Posts: 21 Karma: 8966 Join Date: Nov 2013 Location: Germany Device: Kobo Aura One, Kobo Aura, Kobo Touch	The update is available in Germany now. I have updated my Aura and Aura HD and so far I like it, no issues at all. The only thing I don't like is the missing chess. BTW The Aura updates twice as fast as the Aura HD.

05-10-2015, 04:55 AM	#184
s4nder Connoisseur Posts: 75 Karma: 546874 Join Date: Sep 2010 Location: Estonia Device: Kobo Aura One	Kobo Nickel still has huge line spacing. I wonder when that'll get fixed, I generally like the font.

05-10-2015, 05:23 AM	#185
GERGE Guru Posts: 733 Karma: 5797160 Join Date: Jun 2010 Location: Istanbul Device: Kobo Libra	I don't think Kobo Nockel is a good text typeface. Too small x-heights.

05-10-2015, 08:23 AM	#186
Joques Addict Posts: 294 Karma: 107414 Join Date: May 2013 Device: Kobo Glo	S4nder, I absolutely agree. I especially like it for reading fantasy fiction.

05-10-2015, 09:42 AM	#188
GERGE Guru Posts: 733 Karma: 5797160 Join Date: Jun 2010 Location: Istanbul Device: Kobo Libra	Kobo checks both file name and metadata. They must both be properly done. I am using TransType 4 for editing metadata but you check them with free FontForge. By the way, objectively speaking Kobo Nickel is a bad text typeface. Spacing between letters is too big and x-height is too small. I don't know who designed it for Kobo but it really isn't good. I am not saying that it is unreadeable, but this is not how a text type should be.