11-12-2019, 11:54 PM | #1156 | |
Grand Sorcerer
Posts: 24,906
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
So, exactly how has Kobo botched rendering of monospace fonts with the RMSDK? |
|
11-13-2019, 05:31 AM | #1157 | |
Resident Curmudgeon
Posts: 74,705
Karma: 130140792
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
|
|
Advert | |
|
11-13-2019, 06:57 AM | #1158 | |
Grand Sorcerer
Posts: 24,906
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
And for the record, this is like saying Windows has a bug because I specified to use "Some Stupid Font" in a book but did not supply the font so that the application could read the font from. |
|
11-13-2019, 09:37 AM | #1159 | |
Member Retired
Posts: 61
Karma: 47166
Join Date: Sep 2018
Device: a lot
|
Quote:
The inability of the kobo KA1 to rendering monospaced text out of the box is not a bug: it's a feature. Well, why Kobo doesn't point out in his web site and on every device box "Beware: This device doesn't supply monospaced type font. It doesn't render monospaced text if fonts are not supplied by the book publisher." Just for fairness. Why are you losing your temper? Last edited by PenguinCEO; 11-13-2019 at 09:48 AM. |
|
11-13-2019, 10:23 AM | #1160 | |
Wizard
Posts: 2,845
Karma: 22003124
Join Date: Aug 2014
Device: Kobo Forma, Kobo Sage, Kobo Libra 2
|
Quote:
You want the font, supply it. It’ll render properly. Thus it’s not a bug. You can pester them for the addition of a monospace font, though I’d suggest being less brusque and dismissive to whoever you talk to via their CS lest your request go in the “special request bin” that gets emptied by maintenance every night. |
|
Advert | |
|
11-13-2019, 10:47 AM | #1161 | |
Member Retired
Posts: 61
Karma: 47166
Join Date: Sep 2018
Device: a lot
|
Quote:
I wrote them a very formal report about eight days ago but without feedback. Maybe my report went to the special bin. Can you ask them for clarifications? Maybe they say something to you. Last edited by PenguinCEO; 11-13-2019 at 11:07 AM. |
|
11-13-2019, 11:18 AM | #1162 | |
Wizard
Posts: 2,845
Karma: 22003124
Join Date: Aug 2014
Device: Kobo Forma, Kobo Sage, Kobo Libra 2
|
Quote:
I have no interest in a monospace font so I won’t ask kobo for it. You know what you need to do to get the performance you want. The idea of this being a bug has been throughly squashed. |
|
11-13-2019, 04:07 PM | #1163 |
Grand Sorcerer
Posts: 7,255
Karma: 65432101
Join Date: Feb 2009
Device: Kobo Glo HD
|
Just for my own clarification, if I put a proper mono spaced font in the proper font directory, and the book calls for mono spaced font, the mono spaced font will be used?
|
11-13-2019, 04:55 PM | #1164 | |
Grand Sorcerer
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
The rest of the workaround/solution is different for kepubs than for epubs. I'm not sure which you use. For kepub this post has more details. Note: If you're not a kobopatch user miss out step 2, but then you would need to set the Kobo [Aa] font menu to 'Publisher Default' to see the mono font in the book. For epub the best approach will depend on whether you're also a kobopatch user.
Just for completion, embedding a monospace font in the standard way will work for both kepub and epub. So, in all, that gives 4 different ways to the same visual result. Whether you like any of them may be another story Last edited by jackie_w; 11-13-2019 at 06:37 PM. Reason: kepub Note: |
|
11-13-2019, 05:54 PM | #1165 | ||
Grand Sorcerer
Posts: 24,906
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
Quote:
|
||
11-13-2019, 06:35 PM | #1166 | |
Grand Sorcerer
Posts: 7,255
Karma: 65432101
Join Date: Feb 2009
Device: Kobo Glo HD
|
Quote:
For epubs, with stock firmware, no special config file settings, no patches... If a font family of monospaced is specified in the epub, and I put a monospaced font in the "fonts" directory, will the font get used? I want to know if I purchase an epub that specifies a non-embedded monospace font, the monospaced font will be used (with no modifications needed). |
|
11-13-2019, 07:18 PM | #1167 | |
Grand Sorcerer
Posts: 6,212
Karma: 16534894
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
Patching firmware isn't compulsory but if you don't, simple edits to each epub will be necessary instead - either manually or via calibre. Last edited by jackie_w; 11-13-2019 at 07:21 PM. |
|
11-13-2019, 07:34 PM | #1168 | |
Resident Curmudgeon
Posts: 74,705
Karma: 130140792
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Quote:
The reason it's a bug is because a monospace font is part of ADE (RMSDK) and Kobo has chosen to leave this out. This means that monospace does not work when it should work. I don't know of any other RMSDK (ADE) that does not work with monospace out of the box. If it was not part of RMSDK, then fair enough, it is and Kobo changed it so monospace does not work. |
|
11-14-2019, 12:21 AM | #1169 | ||
Wizard
Posts: 1,760
Karma: 9918418
Join Date: Feb 2013
Location: Here on the perimeter, there are no stars
Device: Kobo H2O, iPad mini 3, Kindle Touch
|
Quote:
I have to agree with JSWolf on this one. David, you’re simply wrong. The CSS Fonts specification defines five generic “fallback” fonts, and every compliant rendering engine is expected to support them. These are serif, sans-serif, cursive, monospace, and fantasy. This is precisely why a well-crafted CSS font declaration will always end with one of those five values; it translates to, “if you can’t find anything else I’ve listed, use the default for this type of text.” Quoting from the spec, section 3.1.1: Quote:
Now, that said… yes, in an ebook environment, it is good practice to embed any specific font you want to use. If you want some of your text to be rendered in Georgia, some in Helvetica, another part in Zapfino for cursive or handwriting… yes, by all means, include those specific typefaces. I’d never advise otherwise. But the whole reason those defaults exist is that, if you want a serif font but aren’t picky about which one, you can specify “serif” and rely on the system default. And the same thing goes for “monospace.” Last edited by Rev. Bob; 11-14-2019 at 12:24 AM. |
||
11-14-2019, 01:32 AM | #1170 | ||
Wizard
Posts: 2,845
Karma: 22003124
Join Date: Aug 2014
Device: Kobo Forma, Kobo Sage, Kobo Libra 2
|
Quote:
This would seem to indicate otherwise Quote:
Which would mean this is, at best, a deficiency, not a bug. As to whether it’s one kobo should rectify I’ll point out I’ve only seen two people actually requesting it on some actual usage level though others have chimed in to ask why Kobo haven’t corrected the deficiency (mistakenly calling it a bug). |
||
Tags |
pocket app |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Probably a Kobo bug. | eXistenZ | Kobo Reader | 19 | 06-13-2014 09:16 PM |
[Old Thread] Bug in downloading metadata | Dasun | Library Management | 3 | 03-21-2011 07:31 PM |
Possible bug or misfeature when a thread is closed | tompe | Feedback | 7 | 10-05-2010 09:38 AM |