Touch New Firmware and Desktop!

[cutterjohn42]

Originally Posted by the.Mtn.Man

So the update is supposed to fix the storage error, but if your device has the storage error then it can't update? That's ironic.

But my Kobo Touch appears clean (no error message when I cycle the power), so that's not the problem for me. I notice you're in Canada, so maybe the update just hasn't been propagated to the US servers yet.

Actually this is a legitimate limitation. They cocked up, and can't restore db consistency so you've GOT to restore to a known good state BEFORE updating, o.w. you'll be left in the same mess or likely even worse off.

The REAL problem is that this bug occurred at all! They've got some major sw process problems that need to be addressed.

[EDIT]
NEW BUG FFS! PREPEND AT LEAST HTTP:// to IP ADDRESSES AND DOMAIN NAMES FFS!

i.e. IP addr phail whale w/o http:// manually added christ!
[/EDIT]

[rashkae]

Originally Posted by JSWolf

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.

Just the way CSS works. (in conjunction with ADE, which is used by Kobo to display epubs, and which Kobo can only modify in limited ways, per licensing agreements with Adobe.)

It makes perfect sense that Kobo silently appends body {attributes} into an e-book CSS (per user preferences) and ADE uses those as it should to display the books. However, if the body has a class, the values of body.class would then take precedence.

Features are not bugs, even if you don't want them and would rather be without, it's still working as designed. Whether or not this particular idea is bad... I'll leave to the jury. I already said my piece on that.

[cutterjohn42]

...and before you get all excited generically prepending HTTP/HTTPS CHECK IF I've actually already prepended a DIFFERENT supported protocol, although ATM I believe that all it supports is HTTP...

[remcdonald]

Cutterjohn you did notice at the bottom of the extras page where it said very specifically that the things being offered there were experimental and not fully supported by kobo (as of yet). Translation expect it to be a bit buggy and wonky in those features that is not a bug anywhere near the level of the old one and frankly I don't think most of us could care less whether or not the experimental browser requires a little more effort to use.

[frankieGom]

Originally Posted by rashkae

Just the way CSS works. (in conjunction with ADE, which is used by Kobo to display epubs, and which Kobo can only modify in limited ways, per licensing agreements with Adobe.)

It makes perfect sense that Kobo silently appends body {attributes} into an e-book CSS (per user preferences) and ADE uses those as it should to display the books. However, if the body has a class, the values of body.class would then take precedence.

Features are not bugs, even if you don't want them and would rather be without, it's still working as designed. Whether or not this particular idea is bad... I'll leave to the jury. I already said my piece on that.

OK, now that I understand the issue a little better, I need to ask: How should one go on about displaying the fonts as defined in the epub (apart fro making sure the specific font is available in the reader)?

Should there be an option in the reader to over-ride user choice and use embedded fonts if available?

[Nina182B]

After the 1.9.10 update, my Kobo was not registered anymore. I had to unfortunately do a factory reset and to re-register it. Everything was fine afterwards until I bought a book and tried to use ADE to transfer it into the Kobo.

ADE is saying I don't have copy permissions when I try to drag the book into the Kobo bookshelf. Suggestions online tell me to deregister the Kobo from ADE by clicking the Kobo bookshelf on ADE and Ctrl+Shift+E but this doesn't do anything for me.

I was able to deregister my computer from ADE, uninstall ADE, install it again, register computer again, but kept getting the same error. Prior to 1.9.10, I was able to drag books into the Kobo bookshelf.

Does anyone have any suggestions? Especially how to deregister Kobo from ADE.

[taming]

Originally Posted by Nina182B

Does anyone have any suggestions? Especially how to deregister Kobo from ADE.

See the Wiki: https://wiki.mobileread.com/wiki/Kobo...e_using_ADE.3F

[Joe563]

There are two ADE-related folders on the Touch, .adobe-digital-editions and Digital Editions. Delete both of these folders and the next time you use ADE it will ask whether you want to authorize the reader.

[Nina182B]

Originally Posted by Joe563

There are two ADE-related folders on the Touch, .adobe-digital-editions and Digital Editions. Delete both of these folders and the next time you use ADE it will ask whether you want to authorize the reader.

Unfortunately this didn't work for me. I also deregistered my computer, and installed ADE again, registered my computer again, turned off ADE. Then plugged in the kobo, and opened ADE. Waited half an hour and nothing happened. It didn't ask me to add the Kobo. It was as if the kobo wasn't connected.

I'm thinking about doing a factory reset but really don't want to since I already did that yesterday, plus not even sure if that would help since ADE isn't "seeing" my Kobo. Thanks for your input on this.

[PeterT]

When you plugged the Kobo in, was it even detected as a disk drive by the PC?

[Joe563]

I'm thinking about doing a factory reset but really don't want to since I already did that yesterday, plus not even sure if that would help since ADE isn't "seeing" my Kobo. Thanks for your input on this.

Try a factory reset. I have done a test of this and it works.

[voracious71]

I never had the storage problem but Im glad it got fixed for those who did. I am a happy girl because of the page number fix..

[Joe563]

Originally Posted by Joe563

Try a factory reset. I have done a test of this and it works.

After you have done the factory reset and if you have the same copy permission message check your viewing permission for the problem book. To do this select the book in Library view and then the menu icon (small right facing triangle in upper left corner). Select Item Info and under Permissions check Viewing. Some publishers may not allow viewing on an e-reader.

[Dave@Kobo]

Originally Posted by Nina182B

Unfortunately this didn't work for me. I also deregistered my computer, and installed ADE again, registered my computer again, turned off ADE. Then plugged in the kobo, and opened ADE. Waited half an hour and nothing happened. It didn't ask me to add the Kobo. It was as if the kobo wasn't connected.

I'm thinking about doing a factory reset but really don't want to since I already did that yesterday, plus not even sure if that would help since ADE isn't "seeing" my Kobo. Thanks for your input on this.

Are you using ADE on Mac OSX by any chance?

[JSWolf]

Originally Posted by rashkae

Just the way CSS works. (in conjunction with ADE, which is used by Kobo to display epubs, and which Kobo can only modify in limited ways, per licensing agreements with Adobe.)

It makes perfect sense that Kobo silently appends body {attributes} into an e-book CSS (per user preferences) and ADE uses those as it should to display the books. However, if the body has a class, the values of body.class would then take precedence.

Features are not bugs, even if you don't want them and would rather be without, it's still working as designed. Whether or not this particular idea is bad... I'll leave to the jury. I already said my piece on that.

You are wrong again. It's a bug. There's no reason that the font-family in the body cannot be overwritten when a custom font is wanted. None at all. In fact, I've seen other cases with a userstyle.css is used to change the defaults. And what was in userstyle.css was used in place of what was in the book's CSS. So really, it can be done such that this bug doesn't exist. It's not a feature. It's a bug. I'm sorry you feel otherwise, but you are wrong. A bug is not a feature. The problem is that Kobo botched it up in the original two readers and didn't bother to fix it for the Touch.

To be honest, there is a way to fix this bug and it should be fixed. There's no reason to screw up many ePub that come with embedded fonts enabled via the body CSS. Trust me, I've seen publisher ePub that would look silly if the embedded font enabled in the body CSS doesn't work.