![]() |
#316 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 217
Karma: 28060
Join Date: Jul 2011
Location: FRG
Device: PRS-T1
|
Widows and orphans
Widows and orphans are variables which you can define in HTML/CSS. If you use DRMed ebooks, like the ones you would buy at Kobo, it might be a bit difficult to influence. Perhaps it would even be necessary to remove the DRM. I'm not sure, because I've never owned a DRMed ebook.
If you're using "free" ePubs and Calibre it's pretty easy to change. Normally, I wouldn't recommend it though, because of, literally, centuries old conventions governing the layout of PRINTED material! So, if you're using an ereader configured to display roughly the same amount of text you might find on a paperback page, don't touch! It'll look pretty much like what the publisher intended. I'm using these "normal" settings and never got pis*ed enough to start editing. But, you've really raised an interesting question here! Being allowed to increase the font size is afterall a much vaunted feature of ereaders. Now that I think about it, quite a large proportion of posts on the forum are concerning greater font flexibility! I haven't found a font-size-speciffic "w. and o." tag or function in HTML/CSS yet, but I'm guessing it might be real hard to implement cross-platform. Since the reading applications on ereaders are nothing but glorified(or stunted) HTML viewers, one likely easy way to make it work would be proprietary. At a certain, device-speciffic, font size(the one where it begins to look ridiculous) the reader app just ignores widows and orphans. Ah, well I'm gonna concur, my eyes aren't getting any better. |
![]() |
![]() |
![]() |
#317 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
|
Actually widows and orphans is easy to put in a CSS. You can do it in the body tag. ADE defaults to 2 for each in the absence of an entry in CSS.
|
![]() |
![]() |
![]() |
#318 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 274
Karma: 1029955
Join Date: Feb 2009
Device: Palm IIIx, EBM-911, REB-1100(dead), PRS-505
|
I guess that you can drop the download progress bar request as I finally saw one the other day, briefly. I guess most of the time my downloads finish before I can click download in the dialog box that pops up asking what to do.
So now, maybe a download history item would be nice... |
![]() |
![]() |
![]() |
#319 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 217
Karma: 28060
Join Date: Jul 2011
Location: FRG
Device: PRS-T1
|
Quote:
Like I said I never had a Kobo or a Kobo ebook(Kpub I think you call them). So if I'd like to change any Kobo Kpub's widow&orphan settings all I would have to do is put it in(I guess inside) the <body> tag of the CSS, like: <body> widows: 2 orphans: 2 blablabla....your ebook, whatever... </body> This being the the CSS file to which every Kobo user has easy access to, right? |
|
![]() |
![]() |
![]() |
#320 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 217
Karma: 28060
Join Date: Jul 2011
Location: FRG
Device: PRS-T1
|
Nope, it just doesn't work that way, sorry! Tried it out, no go. But you can edit these particulars using Calibre and drm free ebubs. Back to the POINT.
It's a pagination issue, ergo: Amazon recently introduced a brand new way of making everyting concerning page numbers standard(ha!). I don't know if it's a replacement of the so called "real page numbers" on the Kindle(which are bs!) but it is (sort of) new. "Kindle Print Replica Content" they call it. Each page in a Print Replica book has the same words and images in the same positions as the corresponding print edition. There you have it, I refuse to count the number of "corresponding print editions" anyone, including KOBO, has, that do not correspond! I'd likely not be alive by then(old age in this case). |
![]() |
![]() |
![]() |
#321 | |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 165
Karma: 339490
Join Date: May 2010
Device: nook, BlackBerry
|
Quote:
|
|
![]() |
![]() |
![]() |
#322 | |
Groupie
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 165
Karma: 339490
Join Date: May 2010
Device: nook, BlackBerry
|
Quote:
First off, it's based on XHTML and CSS, not HTML. But even with that, if you created a 100% valid XHTML/CSS file set, it might not be a valid EPUB. And if you created a 100% valid EPUB file, it might not be valid HTML. The two standards have significant overlap, but each also has several of its own tags. For example, the "display" element in CSS doesn't have "oeb-page-head" or "oeb-page-foot" properties, which exist in OPS (part of EPUB). Meanwhile, the "display" element in CSS has "inline-block", which is not valid OPS. Also, the XHTML/CSS file set won't have a manifest or structure definition, which is defined in the OPF standard--another part of EPUB. The rendering engine (ADE in most but not all cases) knows how to extract the components of the EPUB file, read the manifest, find all the components including embedded fonts, images, etc., and turn it into a book with pages. This is very different than a web browser, which doesn't even break an individual web "page" into individual screen-sized pages. It just flows them infinitely (until it runs out of memory) and puts a scroll bar on the side. |
|
![]() |
![]() |
![]() |
#323 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
|
A CSS file entry would look like:
body {widows:1; orphans:1;} just like every other CSS entry in the CSS file. Note that 2 is exactly the default value so there would not be any difference in the current behavior if you used 2. Dale |
![]() |
![]() |
![]() |
#324 | |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 217
Karma: 28060
Join Date: Jul 2011
Location: FRG
Device: PRS-T1
|
Quote:
I don't give a care! Kobo did(or used to be) making it really dramatic about introducing the NEW KOBO TOUCH to the European market with the long promised searching feature and the localized dictionary functions. They do have licence to lie, I guess. Every other IT bis does. I guess it's just another smokeware. And if it ain't? Why ain't there any hacks. It took a week to hack any other divice |
|
![]() |
![]() |
![]() |
#325 |
Junior Member
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 7
Karma: 3536
Join Date: Aug 2011
Device: Kobo Touch
|
I am not a native English speaker, so the dictionary is very important for me...
All the following features are in Kindle but not in Kobo: *) Show a smaller dictionary window, instead of using up the whole screen. *) Cross look-up in dictionary, i.e. dictionary within dictionary. *) Support custom user dictionaries, e.g. English-to-Chinese. *) An option for going-to-the-dictionary-directly when you press a word, instead of showing a menu of dictionary / highlight / facebook actions. It will be even better if one can add unknown words to a custom list. Thank you. p.s. the page number bar at the bottom is taking up too much spaces above it, especially when the page margin is set to be low. Last edited by kanex; 08-29-2011 at 09:52 AM. |
![]() |
![]() |
![]() |
#326 | |
Séduisant
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 4,706
Karma: 2107018
Join Date: Jan 2010
Location: Texas, USA
Device: Boox Note Air2+; Kobo Libra2; Kindle Scribe, Oasis3; iPad Mini6
|
Quote:
Again, thanks for bringing this up. |
|
![]() |
![]() |
![]() |
#327 |
Gadgetoholic
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 1,467
Karma: 3865860
Join Date: Feb 2011
Location: Sweden
Device: Kobo Libra2, Tolino Vision 6
|
I don't want to appear impatient... or maybe I do...
SEARCH FUNCTION! (From within a book) (Yeah, I know, it's been mentioned by many, but it's really really really important to get it fixed! Long overdue already!) |
![]() |
![]() |
![]() |
#328 |
Junior Member
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 7
Karma: 3536
Join Date: Aug 2011
Device: Kobo Touch
|
and, add a function: lock the screen when the home button is kept pressed...
then one can wipe dusts off the screen without accidentally turning pages! ;-) Last edited by kanex; 08-29-2011 at 10:44 AM. |
![]() |
![]() |
![]() |
#329 |
Wizard
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 2,454
Karma: 5469320
Join Date: Jul 2010
Device: Kobo
|
I agree with accidentally turning pages when doing this, but really, since sleep mode is virtually instantaneous and just as easy I can't see this being a priority.
|
![]() |
![]() |
![]() |
#330 |
Addict
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 205
Karma: 2595216
Join Date: Aug 2011
Device: Clara 2E, Glo HD
|
It's a small thing and I'm not sure if it has been mentioned but:
Could the Sleep/Off stripe be either moved, removed or just made smaller? If one sees the cover of a book it's either because the Kobo is in sleep mode or is off. You have to slide the switch either way and I like to see the covers in all their e-ink glory. OK, maybe a toggle. Thanks Kobonaughts, -V- |
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kobo future firmware feature request thread | sabredog | Kobo Reader | 2239 | 08-24-2025 04:33 PM |
Kobo future Hardware feature request thread | Psyke | Kobo Reader | 1 | 01-07-2011 06:09 PM |
Feature request / Good idea for future versions of Calibre | rahulm | Calibre | 9 | 07-18-2010 06:35 PM |
[Old Thread] Calibre 'feature request' thread | Waba | Calibre | 2 | 02-10-2010 07:52 PM |
Feature request thread? | Dahak | Calibre | 1 | 08-02-2009 12:51 AM |