04-26-2018, 06:58 PM | #46 | |
Grand Sorcerer
Posts: 5,582
Karma: 22735033
Join Date: Dec 2010
Device: Kindle PW2
|
Quote:
My (epub2 compatible) epub3 test book displayed standard ligatures in ADE 2 and 3 but not in ADE 4.5. This might be an ADE 4.5 font issue or, more likely, there's a mistake in my CSS. Last edited by Doitsu; 04-29-2018 at 03:52 AM. |
|
04-26-2018, 11:00 PM | #47 | |
Guru
Posts: 850
Karma: 2641698
Join Date: Aug 2008
Location: Taranaki - NZ
Device: Kobo Aura H2O, Kobo Forma
|
Quote:
|
|
Advert | |
|
04-28-2018, 10:44 PM | #48 | ||
Grand Sorcerer
Posts: 6,171
Karma: 16228536
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
Quote:
I don't use ADE so can't test this myself. If what sherman suggests is correct and ADE 4.5 uses Readium for its epub 3 compatibility you might like to try adding Code:
text-rendering: optimizeLegibility; |
||
04-29-2018, 04:30 AM | #49 | |
Grand Sorcerer
Posts: 5,582
Karma: 22735033
Join Date: Dec 2010
Device: Kindle PW2
|
Quote:
I haven't tested this myself, though. |
|
05-02-2018, 09:37 AM | #50 |
Wizard
Posts: 2,608
Karma: 3000161
Join Date: Jan 2009
Device: Kindle PW3 (wifi)
|
An open question.
There is something that may be (or not?) related to OpenType. Long time ago (several years) I had been advised to find a workaround instead of using the font-variant property with this value. For example: Code:
p.small { font-variant: small-caps; } If I understand well, this above CSS value should be used only if the -embedded or recommended- font is able to display small-caps characters. Then the display is made using a process which evokes the one used for ligatures (though this time we use a specific CSS value). Even then, as for OpenType features, some defective renderers may fail to implement this and display normal characters instead of small-caps. Is this correct? Last edited by roger64; 05-02-2018 at 09:53 AM. |
Advert | |
|
05-02-2018, 10:20 AM | #51 | |
Grand Sorcerer
Posts: 6,171
Karma: 16228536
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
Code:
-webkit-font-feature-settings: "liga", "dlig"; I haven't noticed a performance problem on my Kobos. However, I never actually include this specialised CSS directly in my calibre master copy of the epub as I like to keep these as "vanilla" as possible because I use the same epub on my Android devices. I don't use the Kobo Android app. Whenever possible I patch the on-device Kobo default kepub override CSS sheet. If that can't be done I auto-add any Kobo-specific CSS on-the-fly during calibre send-to-device. |
|
05-02-2018, 11:26 AM | #52 | ||
Grand Sorcerer
Posts: 5,582
Karma: 22735033
Join Date: Dec 2010
Device: Kindle PW2
|
Quote:
Quote:
Stylesheet: Code:
body { text-rendering: optimizeLegibility; } /* Common/standard ligatures (liga) */ .liga { font-variant-ligatures: common-ligatures; -moz-font-feature-settings: "liga", "clig"; -webkit-font-feature-settings: "liga", "clig"; font-feature-settings: "liga", "clig"; } /* Discretionary ligatures (dlig) */ .dlig { font-variant-ligatures: discretionary-ligatures; -moz-font-feature-settings: "dlig"; -webkit-font-feature-settings: "dlig"; font-feature-settings: "dlig"; } Code:
<h2 id="sigil_toc_id_1">Common/standard ligatures (liga)</h2> <p>ff fi fl ffi</p> <p class="liga">ff fi fl ffi</p> <h2 id="sigil_toc_id_2">Discretionary ligatures (dlig)<br/></h2> <p>ct sp st ct Th</p> <p class="dlig">ct sp st ct Th</p> |
||
05-02-2018, 05:06 PM | #53 | |
Grand Sorcerer
Posts: 6,171
Karma: 16228536
Join Date: Sep 2009
Location: UK
Device: Kobo: KA1, ClaraHD, Forma, Libra2, Clara2E. PocketBook: TouchHD3
|
Quote:
As long as the font being used contains ligatures (not sure about kerning) the Kobo ADE renderer for standard epubs will display them without needing to add any special CSS. Using the same font and the optimizeLegibility CSS, results in the kepub renderer displaying both ligatures and kerning (if present). The Kobo kepub renderer will do this too, but not the ADE epub renderer. However, it doesn't display the true small-caps glyphs (if any) contained in the font, it "pseudo-manufactures" them from standard glyphs in mixed normal/small size. I don't much like the thick-and-thin look so I prefer to reference a sideloaded true small-caps font rather than embedding it. The CSS does need to be slightly different for kepub and epub so I use the previously-mentioned technique of auto-editing the font-variant: small-caps CSS on-the-fly during calibre send-to-device. |
|
05-02-2018, 10:00 PM | #54 | |
Bookmaker & Cat Slave
Posts: 11,447
Karma: 157030631
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
We've been through a lot, with small-caps, and all sorts of incipits, because of course (somewhat like copyright pages), every bloody self-pub through our doors has their own idea of what's "right." Smallcap incipits; smallcap incipits after scene-breaks. No asterisms or other fleurons for scene-breaks; all scene-reaks with asterisms/fleurons, and so forth. And of course, incipits can go too far, too short, yadda. But, back to SC. Obviously, you have to embed an actual SC font, typically, to get real SC, like Caslon BigCaps, etc. If you don't, you end up with what IME is a mess. You also get problems when you embed a given font, call it, and then, in the PPW family, "publisher font" gets turned off, and you're left hanging. Oh, well. The more we try to do, the more we end up rueing it. Hitch |
|
05-03-2018, 02:29 AM | #55 |
Wizard
Posts: 2,608
Karma: 3000161
Join Date: Jan 2009
Device: Kindle PW3 (wifi)
|
Small-caps display
Even when embedding a font containing true small-caps (Linux Libertine), using the font-variant property yields inconsistent results, due to the inability of some renderers: - One ePub3 shows normal characters (instead of small-caps) with creengine (koreader) while the Calibre viewer displays true small-caps. - The same ePub3 converted to PDF using Prince PDF plugin, show true (not "pseudo-manufactured") small-caps. This recoups Hitch findings above (for once) that it's safer to embed an actual SC font. Sigh... Edit: even at its best (using font-variant AND a compliant renderer) using font-variant has its limitations. I found that the accented small-caps are missing, which make them unusable in some languages. Ex: Carrère > Carrre, Benoît > Benot Last edited by roger64; 05-05-2018 at 02:18 AM. |
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Problem with font subsetting | grumbles | Editor | 17 | 06-20-2014 02:35 PM |
Font subsetting problem | yktan | Calibre | 5 | 09-19-2013 11:00 PM |
Bug in font subsetting | JSWolf | Calibre | 9 | 01-17-2013 09:46 AM |
ePub Font Subsetting | Cygfrydd | ePub | 2 | 08-17-2010 08:53 AM |
Screen darkening over minutes | Gogolo | iRex | 14 | 11-27-2007 04:37 PM |