Touch Kobo Touch Firmware 2.0

[dannyproy]

Originally Posted by Suzanna

I ran into some problems with the old 2.0.0 on Saturday, so did a factory reset, which reverted me back to 1.9.17. I guess I shouldn't have bothered, but I added back a bunch of sideloaded books. (I was reading a sideloaded book at the time, so just added them all back in.)

Well, last night the device upgraded again to the new 2.0.0 and now I can't read any sideloaded content. Attempting to open a book results in the device rebooting.

Sigh. I'm going to have to experiment to see if this happens with all sideloaded content, or just content that's already on the device. I really don't want to have to go through loading everything again, but it looks like I might have to.

Edited to add:

Well, I added a new book via Calibre and it looks like the problem is will all sideloaded content, not just content that was already on the device. I'm getting the shakes just thinking about being without my ereader, so it looks like I'm back to my Kobo Original (since I doubt my daughters will give up their WiFi models) until all this is sorted out.

I also had the same problem whether updated manually via the zip file or through the desktop. The solution I found was to factory reset and take out any SD card so no books are on the kobo then plugin the kobo and upgrade to 2.0 . Once done with insert your SD card to have books added on to the library, or add manually back on to internal memory. It seems 2.0 is not great with upgrading side loaded ebpub libraries and works best generating a new library from fresh.

A word of warning to all about side loaded epubs and shelves, menu navigation was fine until I created 6 new shelves with 20-80 side loaded epubs in each. This caused menu navigation to massively slow down e.g hitting the home button when reading an epub takes about 2 minutes to take me to the home screen, ouch! Similarly browsing shelves is also very sluggish...almost as if multiple shelves with lots of (specifically side loaded?) content is hogging memory resource or CPU cycles. Navigation whilst reading a book is 'fine' observing just the already reported slightly slower page turns on side loaded epubs.

[murg]

Originally Posted by hitmanx

why isnt everone else angry about hyphenated words at the end of most lines?

I use justified text on all my books. The hyphenation has improved for justified text, in that there is now actual hypenated words.

[MacEachaidh]

Originally Posted by hitmanx

why isnt everone else angry about hyphenated words at the end of most lines?

Well, I'm not angry particularly, but I certainly agree with your dislike for the hyphens and the frustration with them. I find right-justified text much easier to read (no idea what the mechanism behind that is), but hyphenation like mac-
hine really diminishes it.

I have quite a number of books where the right-justification appears to be written into the CSS, so the best interim solution I can see would be to have the option to turn the hyphenation off.

Originally Posted by murg

I use justified text on all my books. The hyphenation has improved for justified text, in that there is now actual hypenated words.

I use justified text as my standard setting as well, but I don't see hyphenation as an improvement. Certainly not when it appears to be haphazard, and breaks your reading stride when you have to pause to reconstruct the word.

Originally Posted by WS64

I even posted a new thread, but actually noone seemed to be interested.

Sorry WS64, I would have joined in on the discussion, but I didn't see the thread.

Originally Posted by GvilleBridge

Oh yes! And it would be more terrific if Calibre could read the shelf data and KT recognize the changed shelves. Calibre/KT cooperation in that kind of elibrary management would allow some very rapid adding to shelves (if not creating them) with multiple CTRL-selects.

I'd hate to see the KT being too closely tied to Calibre, certainly to the point of relying on it for functionality. I know I'm very much swimming against the tide on this, but I personally don't like Calibre and don't use it (or particularly want to).

[murg]

Originally Posted by GvilleBridge

It almost seems like they dumped a genuine hyphenation dictionary (was there one?) and are relying on a really clumsy break-it-anywhere rule.

There is a hyphenation dictionary. It's from Adobe.

[murg]

Originally Posted by MacEachaidh

but hyphenation like mac-
hine really diminishes it.

From the Adobe hyphenation dictionary:
LEFTHYPHENMIN 2
RIGHTHYPHENMIN 3

.in3es
m4achi
ma3ch2i.

From this, it looks like if there is no rule for a work, there will be at least 2 chars to the left of the hyphen, and 3 chars to the right of the hyphen.

As to the other definitions, I'm not sure what they mean. I think the dot means that this is a partial word. The numbers appear to be where the hyphens can go, they may be an indicator of how many chars are desired for a break.

It would be interesting to see if it breaks mach-ines differently than mac-hine.

[PeterT]

I have not tried this (and am not sure I really want to risk it) but... the Adobe Hyphenation dictionary contains the following:

LEFTHYPHENMIN 2
RIGHTHYPHENMIN 3

This looks very similar to the values used by TeX and LaTex to control hyphenation; their descriptions are

TeX won’t hyphenate less than \lefthyphenmin characters after the start of a word, nor less than \righthyphenmin before the end of a word; thus it won’t hyphenate a word shorter than the sum of the two minima, at all. For example, since the minima are 2 and 3 for English, TeX won’t hyphenate a word shorter than 5 letters long, if it believes the word to be English

So it is possible that one could change \usr\local\Kobo\hyphenDicts\hyph_en.dic to have a less aggressive hyphenation setup.

Elsewhere I have seen mention that a sum of the two values to larger than 62 will disable hyphenation totally. (Again this was within TeX / LaTeX).

[guma]

Originally Posted by hitmanx

why isnt everone else angry about hyphenated words at the end of most lines?

its either that only a few of us are getting this ridiculous error, or everyone else doesn't care about it... its been mentioned on this thread but no one has commented on it...

ex: "Ad nauseam is a Latin term used to describe somet-
hing unpleasurable which has continued "to [the point of] nausea". Fo-
r example, the sentence, "This topic has been discussed ad nauseam", signi-
fies that the topic in question has been discussed extensively, and that thos-
e involved in the discussion have grown tired of it."

I for one cannot read books like this,

I can't say that I like the fact that they introduced hyphenation with the latest firmware. But I'm not experiencing any hyphenation errors of the kind you are citing either.

Would be nice though to have the option to switch hyphenation off.

[MacEachaidh]

Originally Posted by PeterT

So it is possible that one could change \usr\local\Kobo\hyphenDicts\hyph_en.dic to have a less aggressive hyphenation setup.

And for those of us who don't have the knowledge or intent for deconstructing the underlying files in the firmware, an option of switching the hyphenation off would simply cut to the chase, it seems.

[filmo]

With 2.0 doesn't sometimes becomes does ' t.

[GvilleBridge]

Originally Posted by Jaden

Nope, doesn't work. Justified or not, there will be hyphenation going on...

Disagree. In the book I'm reading, the unusually titled HHhH (a WWII suspense novel and example of metafiction), I get horrible hyphenations with justified text (even using smaller type):

coincide- nce
hone- st-looking
Persona- lly
barb- aric
cons- idered

When reformatted to unjustified, I get no hyphenated words, only phrases like "horse-drawn" or words like "re-engaged" that are normally hyphenated.

I went to another new novel, John Lanchester's Capital, and viewed several pages unjustified and again had no broken words.

It doesn't seem to depend on type size or margin width either. For fun, I made the typesize like 18 pt with really wide margins and again, no broken words.

I don't know what KT would do with, say,

antidisestablishmentarianism

or

Llanfairpwllgwyngyllgogerychwyrndrobwllllantysilio gogogoch

though I see MobilEread put in a space in the last word.

[Jaden]

Originally Posted by GvilleBridge

Disagree. [...]
When reformatted to unjustified, I get no hyphenated words, only phrases like "horse-drawn" or words like "re-engaged" that are normally hyphenated.

[...]

Hmmm... Very strange... My books are always non-justified. And I have hyphenations.

I don't seem to have many strange hyphenations unless the words are very uncommon or unknown (like "soulscape" which was always "souls-cape" instead of "soul-scape" which it should have been).

So for me it doesn't work.

Wonder what makes the difference... if it was true that formatting every book (and/or setting) to non-justified would get rid of hyphenations I'd be more than happy. I really dislike the hyphenations...

[hitmanx]

the reason this bothers me so much is the fact that i have NEVER read anything with hyphens before...

no matter what specific hyphenation dictionary or convention Kobo is using, the rest of the world has adopted word wrap! It just looks better and is easier to read...

OMG, I am sorry if i am getting animated , this simple problem is so frustrating! Its like i am using an apple newton or something else unintuitive from 1987...

[zigzagz]

scoobertron thanks for the tip re:1.9.14, I might give it a try after I download a backup copy of 1.9.11 so I can roll back if necessary.

[Paul Evans]

I’ve just updated the new 2.0 Kobo Touch firmware, but I can now no longer upload files manually using Calibre software from my computer. I upload my notes from rtf files converted to epub using Calibre and then upload to the Kobo also using Calibre. However, after this 2.0 firmware update, after now uploading books to the Kobo using Calibre and then unplugging from my computer, the new epub note files are not anywhere visible on the Kobo.

Can anyone suggest how I can make my epub files visible on the Kobo using Calibre or the Kobo?

Cheers
Paul

[Cottser]

Before I try a factory reset, is anyone else having a huge font size/text size discrepancy between sideloaded epubs and kepubs in 2.0? I'm using the later version, just updated last night.

As soon as I updated, I opened a kepub and it looked like I was reading a large print book. My settings hadn't changed but it seemed like Kobo's type scale did. If I bump the kepub font size down to a reasonable size, then sideloaded epubs show up tiny and unreadable. This is similar to the margin discrepancy but it's probably about 3 levels of font size difference between kepubs and epubs.

I searched the thread but couldn't find any other reports about this issue.

Attached are two images, the first showing a kepub, the second an epub. Exact same font settings for both.