12-21-2012, 06:49 PM | #196 |
Wizard
Posts: 1,047
Karma: 203682
Join Date: Oct 2009
Device: Libre 2
|
|
12-21-2012, 07:39 PM | #197 |
Banned
Posts: 31
Karma: 1141490
Join Date: Dec 2012
Location: Rapid City, SD
Device: Kindles, iPads, Kobo, Nexus 7 and many others
|
I just bought a new Kobo Glo.. I am going to leave it Virgin.. no side loads etc.. I think that way it will work fine.. mine came with the lastest firmware and it works perfect.. I think doing side-loads, mods etc may cause problems and contamination.. maybe not.. but just a thought..
DG |
12-21-2012, 07:48 PM | #198 | |
Wizard
Posts: 1,047
Karma: 203682
Join Date: Oct 2009
Device: Libre 2
|
Quote:
|
|
12-21-2012, 08:30 PM | #199 | |
Banned
Posts: 31
Karma: 1141490
Join Date: Dec 2012
Location: Rapid City, SD
Device: Kindles, iPads, Kobo, Nexus 7 and many others
|
Quote:
DG |
|
12-21-2012, 08:32 PM | #200 | |
Evangelist
Posts: 470
Karma: 112801
Join Date: Aug 2010
Device: Aura H2O (i86, M96C, Mini&Glo, PRS-950, STR, K-Touch, K-DX, K-3)
|
Quote:
If davidfor is correct, and the issue is related to programming stupidity in handling page number boundaries (possible), then a far more appropriate solution would be to deal with the page numbers like my Sony PRS-950, i.e. let text flow to the bottom of the screen and present page numbers as 215/216 when there is a page number break that does not match a screen break. Then Kobo programmers can focus their limited attention on returning to the correct paragraph within the book, regardless of font changes and ignore page-numbers for all other purposes than that for which they are useful - displaying page-numbers that match the printed book. There is no other reason for displaying the page-numbers than to allow readers to match up an e-book with the printed version (and that's only semi-sensible anyway, since publishers will often publish different versions, such as hardback and softback). However, page numbers are useful in an academic environments for citations and for helping students find the same page when some are using e-readers and some using hardcopy, so you have to show them - just don't let them play any role in setting screen boundaries. Last edited by EldRick; 12-21-2012 at 08:43 PM. |
|
12-21-2012, 10:01 PM | #201 | |||
Grand Sorcerer
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
The gap is caused by the settings of the widows and orphans style setting. The "widow" is that last line from a paragraph that appears at the top of the next page. The "orphan" is the solo line at the end of a page. CSS styles support setting the number of lines for both of these. The default is either 2 or 3. Kobo seem to be using 3. What this means is that if a paragraph goes over the end of the screen, and it has less lines than the sum of the widows and orphans settings, it will be pushed onto the next screen. And there will be a big gap at the bottom of the screen. Exactly how big that gap is depends on a lot of things. As well as the widows and orphans settings, it depends on the font and size, line spacing and margins between paragraphs. And probably some other things. So, the device is respecting the design of the book. It does this in the same way as it respects the other settings. To me, this is the correct thing to do. The book designer decided to do it this way. At least I hope it was a conscious decision and not that they forgot. Or worse, didn't know they could do this. Quote:
|
|||
12-21-2012, 10:44 PM | #202 | |
No Comment
Posts: 3,238
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
Quote:
If the default settings are being used, then the book designer isn't involved in the formatting. And face it, almost all ebooks aren't 'designed', they're mashed together with a minimal attempt at design, especially in regards to page layout. Additionally, the whole widows/orphans thing is mostly an artifact from physical books. On an ereader, they really aren't that necessary. |
|
12-21-2012, 11:37 PM | #203 | |
Wizard
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
|
Quote:
|
|
12-21-2012, 11:55 PM | #204 | |
Bibliophagist
Posts: 35,464
Karma: 145525534
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Forma, Clara HD, Lenovo M8 FHD, Paperwhite 4, Tolino epos
|
Quote:
At least if there was agreement that a page is 1024 visible characters would make the page numbering consistent across ereaders which is currently not the case. Regards, David |
|
12-22-2012, 01:20 AM | #205 |
Grand Sorcerer
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
|
12-22-2012, 06:29 AM | #206 | |
Wizard
Posts: 1,775
Karma: 2694823
Join Date: Dec 2011
Location: The Netherlands
Device: Kobo Touch, Glo, Clara HD
|
Quote:
More importantly, I don't think this is the only 'problem' that's going on. After I read this information a while back in a different thread I re-coverted all my epubs to include widow and orphan values of 0. This helped a lot (but did not completely get rid of slightly premature page breaks). BUT. There is a bug of some kind that has been previously mentioned only a few times, where paragraphs that are longer than a page (or very long, I don't know the cutoff) always start on a new page. This meant that the book I was reading at the time (a Stephen King I think, with veeeerrry long paragraphs) frequently stopped only a couple of lines into a page, making me wonder if the chapter had already finished. But no, the next paragraph was just put onto the next page. Now, I cannot remember what firmware this was (not more than 2 version back, maybe just one), but it was definitely not a widow/orphan thing. |
|
12-22-2012, 06:37 AM | #207 |
Groupie
Posts: 190
Karma: 168826
Join Date: Jul 2011
Location: Vancouver, BC
Device: Kobo Aura One
|
So I'm in Vancouver, Canada. Avoiding a long story, I don't deal with the Kobo desktop because it doesn't like my Kobo (or the one before it, this is a replacement. It disconnects from the Kobo after a minute or so and I can never get anything done). Anyway, as a result, I always do everything via wi-fi.
When I update via wi-fi (which I've just done for the third time in three days), I get a software download notification. Each time, it downloads and installs, but says it's still version 2.1.5. But--it also recreates the multiple shelves I've deleted--every time, after each download. Is anybody else experiencing this? I have a Kobo Touch, by the way. |
12-22-2012, 07:58 AM | #208 | |
Grand Sorcerer
Posts: 24,907
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
A little explanation first. The reference stored for the reading position and bookmarks are made up of several parts: - A reference to the chapter - A reference to the file the position is in - A point in that file As a lot of epubs a built with one chapter per file, the first two parts usually look like they are repeating some information, but they are serving different purposes. The point in the file is a series of number separated by slashes and colons. I'm not completely sure what the numbers mean, but it looks like they are counters for walking the HTML/XML tree. If I am right, it is a reference to the end of the first paragraph on the screen. So, using this information, the reader application can work out where the reader is up to and where to put bookmarks. Looking at the database Lynx-Lynx supplied, the current reading position and the bookmark for the page are identical. Same chapter reference, same file and same point. Looking at my database, it is the same. What does this tell me? Not much. If they were different, it would tell me that the calculation for the two types of position was handled in different ways. Then I might have been able to see where the two points actually were in the book and then on the screen. It looks like the code for positioning the bookmark is different from the code for getting to the last reading position and the latter is wrong. My guess would be the code is that an index isn't being incremented at the right place or someone is counting from zero instead of 1. But this doesn't tell me why it works for some people and not for others. |
|
12-22-2012, 08:24 AM | #209 |
No Comment
Posts: 3,238
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
|
12-22-2012, 08:26 AM | #210 | |
No Comment
Posts: 3,238
Karma: 23878043
Join Date: Jan 2012
Location: Australia
Device: Kobo: Not just an eReader, it's an adventure!
|
Quote:
Specifically setting the values to 0 in the CSS body element does work. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Touch Firmware 2.1.1 and Kobo Desktop | tkavan | Kobo Reader | 8 | 09-07-2012 09:50 PM |
Touch Kobo Touch Firmware 1.9.12 | MDK | Kobo Reader | 172 | 02-15-2012 02:56 AM |
Touch Kobo Touch Firmware 1.9.14 | MDK | Kobo Reader | 190 | 12-23-2011 12:12 PM |
Touch Kobo Touch Firmware 1.9.6 | MDK | Kobo Reader | 84 | 07-20-2011 06:15 PM |
kobo firmware | The Terminator | Kobo Reader | 1 | 12-13-2010 06:26 PM |