Touch New Firmware and Desktop!

[SCION]

Originally Posted by SameerH

This release included some database changes, so Calibre needs to recognize and work with them. I think timlegge works on that, I'll try to contact him.

[Nina182B]

Originally Posted by Nina182B

I restarted, and I still didn't see any of my books. I plugged it into the computer to check if my folders of epubs were still there and they were. When I unplugged (after doing the eject steps), the Kobo showed the "Processing Content" black screen. But it's been like that for the past 20 minutes now.

It looks like my kobo is not registered anymore after the update. I'm registering it again and skipped the checking for books process... still didn't work. So I'm registering one more time and will wait for this checking for books (step 3 configuring and syncing) to be over. I hope I can use my kobo after this.

[Keslynn]

Pleased as punch with the upgrade. Yay for no more database errors!

[molman]

Originally Posted by JSWolf

Thank you for your help.

https://www.mobileread.com/forums/showthread.php?t=83384

The version of For the Win that's not for Sony Readers is the one you want. It has Fontin embedded. You'll know it's working very easily. I do hope it works. But if not, then a bug report can be filed while Kobo is working on the firmware and maybe get this fixed one and for all (if it is indeed broken).

It looks like frankieGom beat me to the punch. If his post ->

https://www.mobileread.com/forums/sho...5&postcount=84

doesn't answer your question let me know and I'll give it a whirl.

[JSWolf]

Originally Posted by SameerH

This release included some database changes, so Calibre needs to recognize and work with them. I think timlegge works on that, I'll try to contact him.

Can you bug someone at Kobo to fix the embedded font bug? The bug is that if you put the font-family in the body of the CSS, the embedded font does not display. This is a bug and many ePub that embeds a font family puts the font-family in the body to activate it. This is a serious bug that needs fix.

[JSWolf]

Originally Posted by frankieGom

Fair enough about margins and empty lines, this is your choice. It just struck me as "different" and I wouldn't know whether it was intended.

See the attached image. The page displays like that when I start reading the book, and remains the same as I turn the pages, until I go and pretend to change something in the font menu where it displays correctly ever after (i.e until I exit the book and go back into it).



Uploaded with ImageShack.us

The font isn't showing. So the embedded font bug from the original Kobos still exists. I've posted in this thread about it. So let's see if it gets acknowledged and then fixed. In my opinion it's a serious bug as a lot of ePub that have embedded fonts won't display them.

[JSWolf]

Originally Posted by molman

It looks like frankieGom beat me to the punch. If his post ->

https://www.mobileread.com/forums/sho...5&postcount=84

doesn't answer your question let me know and I'll give it a whirl.

The screen shot was perfect. It showed the bug still exists and as long as Kobo are here and taking bug reports, let's get this one reported so it can be fixed.

[molman]

Originally Posted by JSWolf

The font isn't showing. So the embedded font bug from the original Kobos still exists. I've posted in this thread about it. So let's see if it gets acknowledged and then fixed. In my opinion it's a serious bug as a lot of ePub that have embedded fonts won't display them.

what font should that have been?

[JSWolf]

Originally Posted by molman

what font should that have been?

Fontin is the embedded font.



What is displayed on the Kobo is some sort of sans-serif font.

[rashkae]

Originally Posted by JSWolf

Can you bug someone at Kobo to fix the embedded font bug? The bug is that if you put the font-family in the body of the CSS, the embedded font does not display. This is a bug and many ePub that embeds a font family puts the font-family in the body to activate it. This is a serious bug that needs fix.

This is not a bug, but a feature.

Overwriting the default body attributes is the trick that allows Kobo to use User selectable fonts. (You'll note that you can't do that on the Sony devices.) You can work around it very easily by putting the font-family attribute in the class you assign for the body, rather than right in the body attribute.

(By the way, Calibre does this for you if you do a a conversion of the sample you provided.)

[JSWolf]

Originally Posted by rashkae

This is not a bug, but a feature.

Overwriting the default body attributes is the trick that allows Kobo to use User selectable fonts. (You'll note that you can't do that on the Sony devices.) You can work around it very easily by putting the font-family attribute in the class you assign for the body, rather than right in the body attribute.

(By the way, Calibre does this for you if you do a a conversion of the sample you provided.)

No, it's a bug. People do not program ePub to fit the Kobo. So what happens is that the embedded font(s) either do not display or only partially display. Publishers who do embed fonts (most of the time) put the font-family in the body and this means what's embedded doesn't display. I know you can get embedded fonts to work. But that's a kludge and not correct to have to do instead of using the body CSS entry. If Kobo cannot come up with a better way of doing things, then they should not do them when it breaks things that never should be broken in the first place.


Calibre takes the @font in the CSS and botches it by putting it in every XML. That's not good at all. Using Calibre to go ePub > ePub can cause it's own set of issues. Not recommended at all.

[m_bisson]

I REALLY want to be able to "close" books on the desktop app so that when I sync it doesn't open EVERY single book I have on my kobo.... grr..

[rashkae]

Originally Posted by JSWolf

If Kobo cannot come up with a better way of doing things, then they should not do them when it breaks things that never should be broken in the first place.


Calibre takes the @font in the CSS and botches it by putting it in every XML. That's not good at all. Using Calibre to go ePub > ePub can cause it's own set of issues. Not recommended at all.

I agree to disagree.

[JSWolf]

Originally Posted by rashkae

I agree to disagree.

The more I think about it, the more I see it is a bug. It should not matter that the font-family is in the body style. If Kobo is overriding the body style then why does it matter if the font-family is in the body style? It's not being used when it's overridden.

[molman]

@rashkae: I was actually going to ask you point next, how things should be handled when the user elects their own system font preference. I would hate for the ePub to dictate the font over my own selection. Perhaps as you contend this was a design choice on the part of Kobo, though I don't really understand the nuances of what you are both discussing to say either way.