08-01-2017, 01:55 PM | #16 | |
Grand Sorcerer
Posts: 27,552
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
|
|
08-01-2017, 03:46 PM | #17 |
The Grand Mouse 高貴的老鼠
Posts: 71,510
Karma: 306214458
Join Date: Jul 2007
Location: Norfolk, England
Device: Kindle Voyage
|
|
Advert | |
|
08-05-2017, 11:11 PM | #18 | |
Bookmaker & Cat Slave
Posts: 11,462
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
If you are dealing with an environment in which you have one font for the drop, and another for the body--which, in turn, can be changed--there's really no good way to address this in eBooks. Every different font has different line heights, x-heights, ascenders, descenders and so forth. Thus, whilst in print you can adapt the two, to get a perfect drop, in eBooks, you're screwed. I would add that whilst you can go bonkers and write a BOATLOAD of media queries for KF8 and KF7, to work around this SOMEWHAT competently, it taks hours to do for each book, if you're using different drop and body fonts, or a different font for the drop, yadda, yadda, yadda. Offered solely FWIW. Hitch |
|
08-09-2017, 03:33 AM | #19 |
Obsessively Dedicated...
Posts: 3,200
Karma: 34977896
Join Date: May 2011
Location: JAPAN (US expatriate)
Device: Sony PRS-T2, ADE on PC
|
Also to note that even simple Large Initial (Up) Caps will increase the line-height of that first line, so that it will often display with a larger gap than the other lines.
Even if you do set line-height to zero, and height: 0. This happens to me if I use a font size any larger than 130%. That feels very restrictive! Why oh why does it feel like they want to render in the old vanilla-plain-text of 20 years ago??? Last edited by GrannyGrump; 08-09-2017 at 03:40 AM. |
08-09-2017, 05:25 AM | #20 |
Resident Curmudgeon
Posts: 73,998
Karma: 128903378
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
Amazon's ignoring of line-height to reduce the line height is just wrong. It makes some eBooks look awful when you get a large first letter. Some books do this not only at the first paragraph, but at the first paragraph after a section break.
|
Advert | |
|
08-09-2017, 07:40 AM | #21 |
Grand Sorcerer
Posts: 27,552
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
This was an EPUB3 thread, in the EPUB forum. I felt quite confident ignoring any possible Kindlebook quirks, with regard to the specs. In my EPUB readers, the line-height trick works for me with raised caps and (sub|super)scripts. But maybe that's because I don't typically use many different fonts (and only use a 3-4em font-size for raised-caps). If the spacing is still different after that, then it's too subtle for my eyes to care about. But regardless ... I see now that pdurrant's wishes were to not have to diddle the line-height attribute when dealing with (sub|super)scripts in the first place.
|
Tags |
asin, epub 3, metadata, onix |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Metadata for PDF magazines - ASIN? other id? | dhdurgee | Library Management | 5 | 02-12-2016 04:21 PM |
Download options for Identifier (isbn, asin, etc.) metadata | digital_carver | Library Management | 14 | 09-06-2015 08:35 PM |
Download metadata from ASIN | CaitlinShaw | Library Management | 3 | 06-17-2015 12:56 AM |
Mobi-asin and metadata | desertblues | Calibre | 6 | 01-20-2013 09:43 AM |
Downloading ASIN from Amazon | nynaevelan | Library Management | 6 | 02-02-2012 09:53 PM |