09-18-2013, 09:03 AM | #1 |
Member
Posts: 12
Karma: 10
Join Date: Sep 2013
Device: Amazon Kindle Paperwhite 2
|
Kobo page fitting
After reading a lot about both the new Aura and the Paper White 2, I am about to preorder the Aura. My main hangup is that in every video you can see the book's title on top of every page, and a huge main at the bottom. I assume you can get rid of the title, but, can you format the book so that the bottom margin is reduced to a minimum? Are there any pictures showing that?
Thanks in advance. |
09-18-2013, 09:07 AM | #2 |
Addict
Posts: 205
Karma: 459093
Join Date: May 2011
Device: Kobo Aura, Mini, Glo, & Aura HD, KPW, Nook Glow, Nook HD
|
No, you can't change the empty space at the bottom of the page. And you can't get rid of the title on top of the page. This is for the Aura HD, despite preordering the Aura August 28th and them charging my credit card the 12th of September I haven't seen one (or even a shipping notice) yet. But that extra space at the bottom is a common complaint for the Aura HD.
|
Advert | |
|
09-18-2013, 09:21 AM | #4 | |
Wizard
Posts: 1,474
Karma: 14328611
Join Date: May 2009
Location: Tokyo, Japan
Device: Aura, Aura H2O, Kindle PW3
|
Quote:
|
|
09-18-2013, 10:09 AM | #5 | |
Member
Posts: 12
Karma: 10
Join Date: Sep 2013
Device: Amazon Kindle Paperwhite 2
|
Quote:
|
|
Advert | |
|
09-18-2013, 10:23 AM | #6 |
Grand Sorcerer
Posts: 12,119
Karma: 73448614
Join Date: Nov 2007
Location: Toronto
Device: Nexus 7, Clara, Touch, Tolino EPOS
|
Why?
It's not as if Kobo do not know what they are doing or why. All he has done is to provide a means to alter some of their functionality, either by editing some HTML / CSS entries in the binary that happen to be obfuscated by being compressed in zLib format, or by changing some branch instructions in their actual compiled code. Remember; it's not as if the PROGRAMMERS normally have any say in how the layout looks on the device. |
09-18-2013, 10:30 AM | #7 |
Member
Posts: 12
Karma: 10
Join Date: Sep 2013
Device: Amazon Kindle Paperwhite 2
|
So you are telling me that they keep that disgraceful blank space and that awful long paragraph bug because they like the way it looks? They should allow the user more customisation IMHO.
|
09-18-2013, 01:17 PM | #8 |
Always been the caretaker
Posts: 479
Karma: 1406369
Join Date: Dec 2012
Location: Canada
Device: Aura H2O, PW2
|
Customization would be awesome. Full page mode would be one of those easy (I should think) things to implement on Kobo's part that would make a noteworthy selling feature.
|
09-18-2013, 01:39 PM | #9 |
Addict
Posts: 255
Karma: 1151364
Join Date: Aug 2009
Device: Aura HD and H2O
|
I have an Aura HD and I applied the patch within the first day: https://www.mobileread.com/forums/sho...d.php?t=220171
I would not want to go back to the eyesore and clumsiness of wasted space at the bottom. There is a screenshot in post #13 of the patch thread. The HD has been out for a while, and Kobo seems unwilling or unable to do anything about some of the rendering bugs. |
09-18-2013, 02:24 PM | #10 |
Zealot
Posts: 132
Karma: 1070185
Join Date: Mar 2013
Location: Italy
Device: Kobo Aura HD
|
I actually love the space, I don't feel like the screen is cluttered, i really don't care about turning 1-10 more times... Honestly is much more clear this way for me. (I've never had the long paragraph bug, also).
|
09-19-2013, 12:07 AM | #11 | ||
Grand Sorcerer
Posts: 24,908
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
Quote:
And Peter emphasised the word "PROGRAMMERS" for a reason. A programmer on a large project rarely has a say in what gets implemented. They get a task that says "implement this". How much detail they get depends on how the project is run and the actual programmer. A junior programmer might get it spelt out almost to the code level. A senior programmer will get more freedom. But that freedom will be to design something to a defined set of specifications. The programmer might be able to change some things, but will usually need to put these back through the change control process to get the are accepted. I'll make a comment on the "Kobo should add these as options" that is everyone's opinion. That isn't as easy as it sounds. And adding options to existing code can be even harder. If we add a new option, say one to not display the title in kepubs, this is what needs to be done: - Decide where to display the option - Word the text and any help for the option - Add code to read and save the option as part of the settings - Add code to use the option - Unit test the change to make sure it does what is intended - Test the change as part of the product to make sure it works and doesn't break something else The above is a simplification. And the first two steps are a lot more important than you think and can lead to a lot of discussion in the development team. The testing is also a problem. Adding the option suddenly doubles the testing of that module. They need to test with the option set and without. If they also added an option to hide the page number, there is suddenly four combinations to test. All the above means that adding features to an existing code base is not as simple as it might seem. Bug fixes are usually handled differently. Someone gets a list of reported bugs, tests them to see if they can be reproduced, verifies they are actually bugs (the widows and orphans handling is not a bug, but the long paragraph handling is) and then prioritises them. Then, they are handed to the programmers to fix the bugs in order of priority. The highest priority bugs will always be "can't use the system" or data loss. As annoying as the long paragraph bug is, it will be a low priority. The book can still be read but will need a few more page turns. Should Kobo hire the author of the patcher? I have no idea. What he is doing doesn't necessarily demonstrate any programming skills. It demonstrates the ability to read the compiled code and work out what can be changed. That is an impressive feat, but doesn't actually say the author can write code in the language that Kobo develops in. |
||
09-19-2013, 04:44 AM | #12 |
Guru
Posts: 729
Karma: 3822612
Join Date: Sep 2009
Location: Sweden
Device: Paperwhite 2, Kobo Aura H2O
|
With Bookeens Cybookreaders you are able to hide bothe the page numer and the title header of a page which would be nice for the Kobo.
|
09-19-2013, 11:03 AM | #13 | |
Fanatic
Posts: 598
Karma: 641742
Join Date: Mar 2012
Location: DE
Device: Kobo Glo
|
Quote:
This is imo what Kobo should keep more in mind and give users more control to enable or disable options or features. As I and others have mentioned earlier, other ereader manufactures have implemented similar features but in a more customizable way. I don't know either but I do know that he touched a chord as it is one of the most popular kobo patches available. To hire or not to hire but this should tell Kobo that something needs to be done with the amount of screen space the header/footer hijacks from the actual screen space available for reading. And yes, showing book information in a header and footer can be useful but is not a necessity. The patch "proved" that reducing (not hiding!) the margins of the footer did not encumber the readability of the displayed footer text. True. But there are many little tweaks available for more experienced users by modifying the kobo.conf configuration file. The question is: Why are these tweaks not accessable through the GUI? And no, I don't mean every single one of them, but the most useful should be accessable through the GUI. The Reading settings section of the GUI should enable/disable:
Just to name a few. No technical features or features for developers only. Last edited by Anak; 09-20-2013 at 09:17 AM. |
|
09-19-2013, 11:37 AM | #14 |
whippet addict
Posts: 380
Karma: 689884
Join Date: Dec 2011
Location: France, Normandy, Gisors
Device: Kobo Glo, Kobo Aura 6", Kobo Glo HD, Kobo Aura One, Kobo Sage
|
I, for one, like the "look" of the page setting. It feels like a paper book this the page number at the bottom and it doesn't bother me to turn pages a bit more. I would rather not have crammed full pages, it feels oppressive to me (and yet I have set a very small font on my reader as I can't stand a big font either). But I can understand that my likings are not everyone likings...
|
09-19-2013, 01:47 PM | #15 |
Wizard
Posts: 1,196
Karma: 3765734
Join Date: Feb 2012
Location: Ottawa, Ontario, Canada
Device: Kobo Libra 2, Lenovo Tab M10 FHD Plus, Lenovo Tab M8 HD
|
I'm with you, vice-versa. The top & bottom margins have never bothered me. It's exactly the same layout as pretty much every paperback novel I've ever owned. I suppose that part of it is that for whatever reason I don't recognize the bevel as part of the "page". Still, everyone has their own preferences.
|
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Free (nook/Kindle/DRM-free@XtianBk/Kobo) The Fitting Room [Christian Spiritual Guide] | ATDrake | Deals and Resources (No Self-Promotion or Affiliate Links) | 1 | 04-16-2012 07:56 PM |
PRS-350 Found: excellent fitting inexpensive case | glazwegian | Sony Reader | 8 | 06-20-2011 11:35 AM |
PRS-350 Fitting replacement stylus for the 350 | adbosch | Sony Reader | 4 | 06-02-2011 05:40 PM |
PRS-600 How to make perfect fitting pdf | Belanna | Sony Reader | 1 | 10-30-2009 07:57 AM |