Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Software > Sigil

Notices

Reply
 
Thread Tools Search this Thread
Old 09-16-2012, 10:45 AM   #46
theducks
Grand Sorcerer
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 15,269
Karma: 6022733
Join Date: Aug 2009
Location: (The original) Silicon Valley, USA
Device: Galaxy Tab 2, Astak Pocket Pro, K4NT
Quote:
Originally Posted by Oldpilot View Post
Oh, I couldn't agree more! Drop-caps remind me of medieval monks illuminating their manuscripts, and I have a happy feeling that I am settling into a soft chair by an open fire and sharing ideas with someone who cared how his (well, all the monks were male!) books actually looked.

You may have noticed, on the KDP forum this morning, that the KF8 update for the Kindle K3 keyboard reader seems to render drop-caps four lines deep, though the cap itself is scarcely three lines high, resulting in a rather silly effect whereby the cap sits to the left of lines 2 and 3 rather than at the top of the paragraph. Of course, this may have been only Punchy Gonzalez's CSS, but it confirms my decision to steer clear of drop-caps for the time being.
ADE will do that effect if you have the wrong Line-height called for your DC to main body font. It is a PITA to get it to look right, only to see some other reader SW render it totally different
theducks is online now   Reply With Quote
Old 09-16-2012, 01:06 PM   #47
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 9,540
Karma: 44002482
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Oldpilot View Post
You may have noticed, on the KDP forum this morning, that the KF8 update for the Kindle K3 keyboard reader seems to render drop-caps four lines deep, though the cap itself is scarcely three lines high, resulting in a rather silly effect whereby the cap sits to the left of lines 2 and 3 rather than at the top of the paragraph. Of course, this may have been only Punchy Gonzalez's CSS, but it confirms my decision to steer clear of drop-caps for the time being.
It almost certainly was Punchy's Gonzalez's CSS.

Mainly because there is no difference in the way "drop-cap" code is rendered across the various devices that support KF8. In fact, the various renderers have no idea what drop-caps are.

The issue is line-height. And the default line-height is much larger on eInk devices that support KF8 when compared to the line-height on Kindle Fire devices. But there's absolutely no reason why the exact same drop-cap code would render any differently on a updated K3 than it would on a Kindle Touch. And users know (or are learning) that they can easily adjust the line-height when they come upon a KF8 book.

Last edited by DiapDealer; 09-16-2012 at 05:32 PM. Reason: typo
DiapDealer is online now   Reply With Quote
Old 09-16-2012, 05:29 PM   #48
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 2,669
Karma: 15346071
Join Date: Apr 2010
Location: Phoenix, AZ
Device: Kindle2, iPad, KindleFire and NookColor
Quote:
Originally Posted by DiapDealer View Post
I almost certainly was Punchy's Gonzalez's CSS.

Mainly because there is no difference in the way "drop-cap" code is rendered across the various devices that support KF8. In fact, the various renderers have no idea what drop-caps are.

The issue is line-height. And the default line-height is much larger on eInk devices that support KF8 when compared to the line-height on Kindle Fire devices. But there's absolutely no reason why the exact same drop-cap code would render any differently on a updated K3 than it would on a Kindle Touch. And users know (or are learning) that they can easily adjust the line-height when they come upon a KF8 book.
And, of course, line-height can be set. I saw Punchy's post. I'm debating on whether or not to reply, given that old Punch has now decided that he's a professional ebook-maker. Of course, I don't remember if his "go-to" tool, Jutoh, lets you set line-height in their quasi-CSS settings.

Hitch
Hitch is offline   Reply With Quote
Old 09-16-2012, 05:33 PM   #49
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 38,541
Karma: 19637653
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Aura H2O, Sony PRS-650, Sony PRS-T1, nook STR, iPad 1, iPhone 5
Quote:
Originally Posted by Hitch View Post
And, of course, line-height can be set. I saw Punchy's post. I'm debating on whether or not to reply, given that old Punch has now decided that he's a professional ebook-maker. Of course, I don't remember if his "go-to" tool, Jutoh, lets you set line-height in their quasi-CSS settings.

Hitch
But, the KF8 code in the eink Kindles ignores Line-height and has a larger then standard line-height. So if you do a drop caps that looks good on an eink Kindle, it won't look good on a Kindle Fire.
JSWolf is offline   Reply With Quote
Old 09-17-2012, 10:44 AM   #50
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 9,540
Karma: 44002482
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by JSWolf View Post
But, the KF8 code in the eink Kindles ignores Line-height and has a larger then standard line-height.
No. The eInk Kindle reader does not ignore the line-height attribute... it just doesn't honor line-height values less than 1.2em or 120%. Nor does the Kindle Fire's reader, for that matter (section 3.1.7 of the Amazon Publishing Guidelines).

Yes, there is a fundamental discrepancy in the default, user-adjustable, line-spacing setting on eink Kindles compared to the Kindle Fire's reading app, but that doesn't have anything to do with the internal CSS line-height attribute specified in the ebook. It's an issue of scale. And it can be overcome by the user simply choosing a smaller line-spacing setting.

Last edited by DiapDealer; 09-17-2012 at 10:50 AM.
DiapDealer is online now   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Override ePub CSS with userStyle.css? barium Sony Reader Dev Corner 11 07-16-2011 04:25 PM
epub CSS versus "Regular" CSS konrad ePub 4 02-18-2011 10:29 AM
css pseudo elements and adjacent combinators in extra css? ldolse Calibre 2 12-21-2010 06:09 PM
help with css bobcdy ePub 2 02-13-2010 12:59 PM
Dropcaps example in User Manual FAQ jackie_w Calibre 7 10-28-2009 07:52 AM


All times are GMT -4. The time now is 03:34 PM.


MobileRead.com is a privately owned, operated and funded community.