Kobo future firmware feature request thread - Page 89

davidfor · 06-30-2016, 12:11 AM

@TNT_69: Requesting the image in random threads across the forum is only going to annoy people. If the idea is to post in places that you think someone who has an image is likely to see, then your first post was a better bet than the later posts. But, your first post was still in the wrong place. It was a thread devoted to the Kobo WiFi. You have a Kobo Touch 2. As there isn't a thread devoted to image requests for that device, you should have started a new thread. That is far more likely to be seen by someone who can help than posting in other threads.

One question: Have you done a factory reset?

DNSB · 07-01-2016, 03:51 AM

Quote:

Originally Posted by Andrew Ashling

I'd like for Kobo to fix the dropcaps settings in the Kobo Glo HD & Kobo Aura H2O.

They were perfect on the Kobo Glo (and I checked on the Onyx Boox C67ML Carta2 which renders them also perfectly), but somehow the dropcaps of the same books are too high on both the Glo HD and the Aura H2O.

I've seen the same issue in several ebooks where some (expletive deleted) munged the CSS by using absolute units instead of relative units. So a dropcap that was specified in pixels might look good on a Glo (768x1024) but not on a H2O (1080x1430) or Glo HD (1072x1448). The same lack of thought that leads to image sizes specified in pixels so they are look decent on a Touch (600x800), a bit small on a Glo and downright tiny on a H2O or Glo HD.

Sample code for both styles:

Code:

span.dropcap {
    float: left;
    font-size: 72px;
    line-height: 56px;
    padding-top: 3px;
    padding-right: 6px;
    padding-left: 3px;
    font-family: "Times New Roman";
    }

Code:

span.dropcap2r {
    float : left;
    font-size : 3.07em;
    margin-top : -0.45em;
    margin-right : 0.05em;
    margin-bottom : -0.5em;
    line-height : 1.5em;
    }

I have seen some blame placed on Kobo for following the ebook specified style (a shocking thought!) and not scaling pixels to compensate for the screen resolution changes. An issue that can so easily be avoided by using relative measurements which scale.

TNT_69 · 07-01-2016, 01:34 PM

Thank you davidfor. Yes I tryed a factory reset. I'll open a new thread!

AndrewH7 · 07-02-2016, 06:08 AM

Quote:

Originally Posted by TNT_69

Any one to help me to get a Kobo Touch 2.0 SD image? Thx in advance.

I've SD from inside my Kobo Touch you my have for price of empty 1 (2gig). Guess I could copy it?

davidfor · 07-02-2016, 08:53 AM

Quote:

Originally Posted by AndrewH7

I've SD from inside my Kobo Touch you my have for price of empty 1 (2gig). Guess I could copy it?

If the card is a 2GB card, that suggests your Touch is an N905B or N905C. TNT_69 is after a card for the Touch 2. This was only released last year and uses completely different hardware.

AndrewH7 · 07-08-2016, 04:19 AM

Quote:

Originally Posted by davidfor

If the card is a 2GB card, that suggests your Touch is an N905B or N905C. TNT_69 is after a card for the Touch 2. This was only released last year and uses completely different hardware.

O! sorry, I didn't go & check if I'd a N°2.

AndrewH7 · 07-08-2016, 04:31 AM

The Kindle shows them okay; found 1 it doesn't show; = w with 2 vertical lines; Kindle just shows it as a 'w'.
So could we have Kobo show a letter sans accent if it doesn't have that letter-accent combination? instead of squares.

TNT_69 · 07-15-2016, 02:48 PM

Quote:

Originally Posted by davidfor

If the card is a 2GB card, that suggests your Touch is an N905B or N905C. TNT_69 is after a card for the Touch 2. This was only released last year and uses completely different hardware.

The card inside my Kobo touch 2.0 it's 4Gb.

WolfBack · 07-21-2016, 04:28 PM

I hope for a Greek language support and hyphenation.
Fortunately, KOReader works very well with greek hyphens. I hope nickel will be support this feature in near future...

davidfor · 07-21-2016, 08:34 PM

Quote:

Originally Posted by WolfBack

I hope for a Greek language support and hyphenation.
Fortunately, KOReader works very well with greek hyphens. I hope nickel will be support this feature in near future...

If you load a Greek font on the device, you should be able to use that to read Greek books. For hyphenation, adding a appropriate hyphenation dictionary might get it working. There is some discussion on this here, but I cannot remember if hyphenation dictionaries for other languages work.

WolfBack · 07-22-2016, 04:18 PM

Quote:

Originally Posted by davidfor

If you load a Greek font on the device, you should be able to use that to read Greek books. For hyphenation, adding a appropriate hyphenation dictionary might get it working. There is some discussion on this here, but I cannot remember if hyphenation dictionaries for other languages work.

Thanks, davidfor!
Kobo is supporting greek fonts and text languages by default in all of my books. Except some font families, by the way... In that case, I use my own fonts and works very well.
My thought is about the interface language. I don't have problems with the English default language that I'm using right now, but I'm really care about the hyphen in my language...
I will try to find a way about. I'm some confusing right now, but I will give a try on this. I have the .oxt and .dict file of greek hyphen (from openoffice site) but it won't work with "hyphenate this" in calibre... Something's goes wrong with UTF8...

AndrewH7 · 07-29-2016, 04:01 AM

Quote:

Originally Posted by WolfBack

I hope for a Greek language support and hyphenation.
Fortunately, KOReader works very well with greek hyphens. I hope nickel will be support this feature in near future...

1 needs to either save text file as Unicode & use a Greek (7PHK) typeface, or save as HTML with Greek head, then use Unicode 1.

Andrew Ashling · 08-10-2016, 09:34 PM

Quote:

Originally Posted by DNSB

I've seen the same issue in several ebooks where some (expletive deleted) munged the CSS by using absolute units instead of relative units. So a dropcap that was specified in pixels might look good on a Glo (768x1024) but not on a H2O (1080x1430) or Glo HD (1072x1448). The same lack of thought that leads to image sizes specified in pixels so they are look decent on a Touch (600x800), a bit small on a Glo and downright tiny on a H2O or Glo HD.

Sample code for both styles:

Code:

span.dropcap {
    float: left;
    font-size: 72px;
    line-height: 56px;
    padding-top: 3px;
    padding-right: 6px;
    padding-left: 3px;
    font-family: "Times New Roman";
    }

Code:

span.dropcap2r {
    float : left;
    font-size : 3.07em;
    margin-top : -0.45em;
    margin-right : 0.05em;
    margin-bottom : -0.5em;
    line-height : 1.5em;
    }

I have seen some blame placed on Kobo for following the ebook specified style (a shocking thought!) and not scaling pixels to compensate for the screen resolution changes. An issue that can so easily be avoided by using relative measurements which scale.

The books in question, which I coded myself, use relative measurements (em):

Code:

.dropcap {
	font-size : 3.014em;
	float : left;
	line-height : 1;
	margin-top : -0.016em;
	margin-right : 0.05em;
	margin-bottom : -0.317em;
        position: relative
    }

Works fine on Akito (reader for Android), Onyx Boox, websites, and the Kobo Glo. Not on the Kobo Glo HD and the Kobo Aura H2O.

The only difference is the software (firmware) version:

Kobo Glo: 3.12.0
Kobo Glo & Kobo Aura H2O: 3.19.5761

Somewhere between those two versions they botched up how dropcaps are handled.

The blame is entirely Kobo's.

JSWolf · 08-11-2016, 04:04 AM

Actually, it may not be Kobo's fault. Maybe it's the fault of RMDSK using in 3.19.5761 vs RMDSK using in 3.12.0.

Larla · 08-18-2016, 12:31 PM

I would request a change in Kobo's handling of fontsize on a per book basis. If I understand what is currently supported (as stated by davidfor in a separate thread) the firmware does this:

1) When the fontsize is changed it is written to the book database and to the global config
2) When a book is opened, the fontsize is read from the book database and if it doesn't exist there it is read from the global config

I think one additional rule should be added:

1) If the book just opened has to read its fontsize from the global config (per rule 2 above) it should then write this fontsize to the book's database

This will insure that every book has a recorded fontsize that the user is happy with.

I'm not sure exactly where this functionality lies: the epub & kepub readers or in some global area of the firmware.

ps: davidfor -- let me know if I have stated things correctly.

07-08-2016, 04:31 AM	#1327
AndrewH7 Enthusiast Posts: 31 Karma: 10 Join Date: Jan 2015 Device: Kobo Touch	Accents The Kindle shows them okay; found 1 it doesn't show; = w with 2 vertical lines; Kindle just shows it as a 'w'. So could we have Kobo show a letter sans accent if it doesn't have that letter-accent combination? instead of squares.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Feature Request	Partzz	Calibre	6	09-09-2010 02:11 PM
Feature request / Good idea for future versions of Calibre	rahulm	Calibre	9	07-18-2010 07:35 PM
[Old Thread] Calibre 'feature request' thread	Waba	Calibre	2	02-10-2010 08:52 PM
Feature request thread?	Dahak	Calibre	1	08-02-2009 01:51 AM
Feature request	AprilHare	Calibre	4	04-22-2009 05:23 AM

06-30-2016, 12:11 AM	#1321
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	@TNT_69: Requesting the image in random threads across the forum is only going to annoy people. If the idea is to post in places that you think someone who has an image is likely to see, then your first post was a better bet than the later posts. But, your first post was still in the wrong place. It was a thread devoted to the Kobo WiFi. You have a Kobo Touch 2. As there isn't a thread devoted to image requests for that device, you should have started a new thread. That is far more likely to be seen by someone who can help than posting in other threads. One question: Have you done a factory reset?

07-01-2016, 01:34 PM	#1323
TNT_69 Junior Member Posts: 8 Karma: 10 Join Date: Jun 2016 Device: Kobo Touch 905C	Thank you davidfor. Yes I tryed a factory reset. I'll open a new thread!

07-21-2016, 04:28 PM	#1329
WolfBack Zealot Posts: 122 Karma: 130628 Join Date: Aug 2015 Location: Athens, Greece Device: Kobo Aura 6'', Kobo Aura H2O, Kobo Glo HD	I hope for a Greek language support and hyphenation. Fortunately, KOReader works very well with greek hyphens. I hope nickel will be support this feature in near future...

08-11-2016, 04:04 AM	#1334
JSWolf Resident Curmudgeon Posts: 80,784 Karma: 150249619 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Actually, it may not be Kobo's fault. Maybe it's the fault of RMDSK using in 3.19.5761 vs RMDSK using in 3.12.0.

08-18-2016, 12:31 PM	#1335
Larla Addict Posts: 281 Karma: 5262189 Join Date: Dec 2011 Location: Katy, TX Device: Samsung Tab S5E 12" Tablet	I would request a change in Kobo's handling of fontsize on a per book basis. If I understand what is currently supported (as stated by davidfor in a separate thread) the firmware does this: 1) When the fontsize is changed it is written to the book database and to the global config 2) When a book is opened, the fontsize is read from the book database and if it doesn't exist there it is read from the global config I think one additional rule should be added: 1) If the book just opened has to read its fontsize from the global config (per rule 2 above) it should then write this fontsize to the book's database This will insure that every book has a recorded fontsize that the user is happy with. I'm not sure exactly where this functionality lies: the epub & kepub readers or in some global area of the firmware. ps: davidfor -- let me know if I have stated things correctly.