06-10-2018, 08:53 AM | #2911 |
cacoethes scribendi
Posts: 5,809
Karma: 137770742
Join Date: Nov 2010
Location: Australia
Device: Kobo Aura One & H2Ov2, Sony PRS-650
|
@NiLuJe very good. I had not noticed that distinction. No LED blinking, just the blinking squares which I had taken to mean a full restart. (To be clear: There is an LED that blinks during a power-on - it does not come on after KOReader exit.) Time difference doesn't seem obvious. (H2O v2 Product ID 378, FW v4.8.11073. kfmon v1.0.0)
|
06-10-2018, 09:00 AM | #2912 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@gmw: I'm going to assume everything's peachy, then .
Note that there may still be something going slightly wonky somewhere, Mark7 handling is still a bit rough around the edges in general . That, or those devices just cold boot significantly faster . |
Advert | |
|
06-10-2018, 09:13 AM | #2913 |
cacoethes scribendi
Posts: 5,809
Karma: 137770742
Join Date: Nov 2010
Location: Australia
Device: Kobo Aura One & H2Ov2, Sony PRS-650
|
@NiLuJe Yes, all peachy on my device.
Maybe the Mark7 is faster, or maybe the fact that I only side-load epubs (there are no kepubs at all on this device at the moment) has an effect? Just guessing. |
06-10-2018, 09:43 AM | #2914 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@gmw: How much time does it actually take? (To cold boot, and to restart nickel on KOReader's exit).
Because if all is well, a restart should take less than 10s. When it takes a bit longer, it usually means that I did something wrong ^^ (or that Nickel is in a mood). EDIT: I'd also ask you for your KOReader version, but with a H2O²r2, it's got to be pretty recent anyway . Last edited by NiLuJe; 06-10-2018 at 09:45 AM. |
06-10-2018, 10:02 AM | #2915 |
cacoethes scribendi
Posts: 5,809
Karma: 137770742
Join Date: Nov 2010
Location: Australia
Device: Kobo Aura One & H2Ov2, Sony PRS-650
|
As per my first post on the previous page, KOReader build 2018.06.02, with that minor config change.
After KOReader exit it's around 6-7 seconds (the first couple of those are still on the open book with no action apparent, presumably KOReader closing down, then about 4s of blink squares). Power up is hard to get an exact start point, but there seems to be about 6s from first LED on until blinking squares, and then about 4s of those until up and running. So we're talking around 3s extra time over all ... very roughly. |
Advert | |
|
06-10-2018, 11:43 AM | #2916 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@gmw: Then yeah, I'd say everything's going according to plan, so, good news .
|
06-15-2018, 03:58 PM | #2917 | |||
Bottom Text
Posts: 146
Karma: 332882
Join Date: Nov 2016
Device: Kobo Clara HD, Kobo Glo HD
|
Quote:
Quote:
Quote:
Would be nice if it would check if the wallpaper directory set in the settings, exists. |
|||
06-15-2018, 06:01 PM | #2918 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@CH23: *huge sigh of relief* .
Yeah, at the very least not horribly crashing would be better, yeah . EDIT: Done . EDIT²: And the matching PR. Last edited by NiLuJe; 06-15-2018 at 08:40 PM. |
06-18-2018, 04:39 PM | #2919 | |
Bottom Text
Posts: 146
Karma: 332882
Join Date: Nov 2016
Device: Kobo Clara HD, Kobo Glo HD
|
Quote:
Didn't have a chance to test this yet, but since it's a very minor adjustment, i doubt it could bring wreckage to the program |
|
06-20-2018, 04:36 PM | #2920 |
Addict
Posts: 250
Karma: 136662
Join Date: Apr 2011
Device: N/A
|
As a general rule, I noticed that the same user font is rendered visibly bolder by KOReader than by Nickel on my KA1-LE. Is this really the case? Can I adjust KOReader to have the same weight as Nickel?
|
06-20-2018, 05:13 PM | #2921 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@hfpop: There's a contrast setting both in Nickel & KOReader. But since they're two different renderers, you probably won't be able to make them agree in every circumstances.
(Although switching KOReader to Native hinting may help close the gap on most decently hinted fonts). |
06-21-2018, 02:30 AM | #2922 |
Librarian
Posts: 346
Karma: 72225
Join Date: Apr 2015
Location: Liège - Belgium
Device: kobo gloHD - KA1
|
@hfpop I've seen threads on the kobo forum about differences in fonts rendering on kindle and kobo (which is more or less the same issue). These things can be corrected by changing one value (panose) in the font with fontforge (but just now I'm too lazy to search it back) ; If I'm not wrong, GERGE is the person you should seek for advice.
There is also some tips at the end of the wiki page for using fontforge : https://wiki.mobileread.com/wiki/Kobo_eReader and IIRC there is a script to "koboify fonts" : the result seems to make them more the same when you use them on nickel and on koreader. Whatever the result, these are some funny things to try :-) |
06-21-2018, 04:11 AM | #2923 |
Wizard
Posts: 2,608
Karma: 3000161
Join Date: Jan 2009
Device: Kindle PW3 (wifi)
|
I never tried to play around with panose values but this could prove interesting to modify side-loaded fonts.
I just took a screenshot of the wiki signalled by cramoisi and of an illustration about panose values. Last edited by roger64; 06-21-2018 at 04:14 AM. |
06-21-2018, 11:35 AM | #2924 |
BLAM!
Posts: 13,477
Karma: 26012494
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
IIRC, some renderers entirely bypass the Panose metadata. I can't remember which though (might be Kindle/M7, Kindle/KF8, might be Nickel/ADE, might be Nickel/kePub, and I don't think we care in KOReader either, because we're not using fontconfig).
Do note that I'm pretty sure this doesn't affect weight at all, it affects what the renderer *thinks* the weight of that font is. i.e., that specific bit in the WiKi is to fix Nickel 'missing' the Book/Medium weight, and instead falling back to bold, and as such rendering (mostly) everything with the bold style of the family. Last edited by NiLuJe; 06-21-2018 at 11:40 AM. |
06-21-2018, 12:49 PM | #2925 |
Addict
Posts: 250
Karma: 136662
Join Date: Apr 2011
Device: N/A
|
Thank you all for your help. I have one more question in the actual file names scheme. The base name of the files have to match the internal font name. In the case given in the cited wiki, I have the following, in FontForge:
Element / Font Info / PS Names: Fontname: AmazonEmber-Regular Family Name: Amazon Ember Name For Humans: Amazon Ember Base Filename: Same as Fontname Element / Font Info / TTF Names: Family: Amazon Ember Styles: Regular Fullname: Amazon Ember The file is saved as AmazonEmber-Regular.ttf, but the windows font viewer sees the font name as Amazon Ember. Question: I should rename the file to read Amazon Ember-Regular.ttf, even if it is saved as AmazonEmber-regular.ttf, right ? Thank you. Last edited by hfpop; 06-21-2018 at 12:57 PM. |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
KOReader: a document reader for PDF, DJVU, EPUB, FB2, HTML, ... (GPLv3) | hawhill | Kindle Developer's Corner | 1268 | 02-27-2024 11:49 AM |
Touch Using two Kobos | tkavan | Kobo Reader | 4 | 06-23-2017 02:47 AM |
2 kobos at once | tsarinaerika | Kobo Reader | 14 | 06-03-2013 04:13 AM |
Syncing between two Kobos | fx3000se | Kobo Reader | 4 | 01-24-2013 02:10 PM |
2 kobos 1 account | retired05 | Kobo Reader | 9 | 05-05-2012 08:25 AM |