Does Atlantis utilize “Media Queries and Hanging Indents” in its creation of Ebook files? I have heard that when incorporated these two elements help to display files in the intended manner on smaller devices and older readers.
Please advise.
Rom.
Media Queries and Hanging Indents
Hi Rom,
From what I read, it seems that use of the so-called “Media Queries and Hanging Indents” is restricted to the Amazon Kindle format. It would be a complete waste of time, and most likely heavily counterproductive to try and use such stuff in other formats than the Kindle format (i.e. in the EPUB format).
So where do we go from here?
Atlantis does not interfere in the creation of the Kindle format, it simply outsources the job to the KindleGen utility (see generate eBooks in the Amazon Kindle (MOBI) format for details).
We can only advise you to download and install the latest version of the KindleGen utility as available from KindleGen. And hope that this KindleGen utility will handle hanging indents the way you expect it to.
HTH.
Cheers,
Robert
From what I read, it seems that use of the so-called “Media Queries and Hanging Indents” is restricted to the Amazon Kindle format. It would be a complete waste of time, and most likely heavily counterproductive to try and use such stuff in other formats than the Kindle format (i.e. in the EPUB format).
So where do we go from here?
Atlantis does not interfere in the creation of the Kindle format, it simply outsources the job to the KindleGen utility (see generate eBooks in the Amazon Kindle (MOBI) format for details).
We can only advise you to download and install the latest version of the KindleGen utility as available from KindleGen. And hope that this KindleGen utility will handle hanging indents the way you expect it to.
HTH.
Cheers,
Robert
-
just2write
- Posts: 8
- Joined: Wed Apr 15, 2015 6:25 pm
Hopefully as HTML 5 becomes more mainstream it will circumvent to some extent the lack of standards between these two warring formats
Here is a quote from Liz Castro’s blog…a bit dated, but still applies:
http://www.pigsgourdsandwikis.com/2012/ ... ry-on.html
“A technical note. There was some concern that you couldn't serve different indents to Kindle Fire and to legacy Kindle because the legacy Kindle code uses the width attribute (in a bizarre way) in the HTML, and not the CSS. But the technique described above works because KindleGen converts the CSS in a good EPUB into the weird, hackish old mobi code—complete with width tag—that legacy Kindles love, but creates "KF8" code for the new Kindle Fire, which, as I mentioned Thursday, is virtually the same as the original EPUB. And EPUB readers will get the original, good, EPUB file. So everyone's happy.
Except designers who have to do twice the work. Think standards don't matter? Think again.”
Regards Rom
Here is a quote from Liz Castro’s blog…a bit dated, but still applies:
http://www.pigsgourdsandwikis.com/2012/ ... ry-on.html
“A technical note. There was some concern that you couldn't serve different indents to Kindle Fire and to legacy Kindle because the legacy Kindle code uses the width attribute (in a bizarre way) in the HTML, and not the CSS. But the technique described above works because KindleGen converts the CSS in a good EPUB into the weird, hackish old mobi code—complete with width tag—that legacy Kindles love, but creates "KF8" code for the new Kindle Fire, which, as I mentioned Thursday, is virtually the same as the original EPUB. And EPUB readers will get the original, good, EPUB file. So everyone's happy.
Except designers who have to do twice the work. Think standards don't matter? Think again.”
Regards Rom