[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook-apps] epub parameters: explain
> Which reminds me: What's the easiest way in your customization layer > to suppress an single instance of a HTML element? I don't understand the question. Can you provide an example of what you are trying to do? Bob Stayton Sagehill Enterprises bobs@sagehill.net ----- Original Message ----- From: "Robert Nagle" <idiotprogrammer@gmail.com> To: "Keith Fahlgren" <abdelazer@gmail.com> Cc: <docbook-apps@lists.oasis-open.org> Sent: Wednesday, December 01, 2010 11:45 PM Subject: Re: [docbook-apps] epub parameters: explain > I've been studying the Mobipocket format (with Joshua Tallent's > excellent book on Kindle formatting). > > Much of the limited styling available for it comes from HTML classes > of elements having to do with presentation. This doesn't seem to be > good semantics and frankly, doesn't seem very compatible with html > generated from docbook. It seems the only way to get an epub ready > for kindlegen is to do a lot of profiling.. > > Which reminds me: What's the easiest way in your customization layer > to suppress an single instance of a HTML element? > > > Robert > > On Thu, Dec 2, 2010 at 1:10 AM, Keith Fahlgren <abdelazer@gmail.com> wrote: >> On Wed, Dec 1, 2010 at 10:53 PM, Robert Nagle <idiotprogrammer@gmail.com> wrote: >>> Hi, I browsed through the docbook.xsl file in the epub directory, and >>> I see some unfamiliar parameters. >> >> Yes, most of them are not actually intended for external customization. >> >>> Most I can guess the function of, but a few left me puzzled. Anyone >>> know what they refer to: >>> >>> epub.cover.linear ? >> >> Some publishers prefer the cover (XHTML file) to be the first document >> displayed to a reader, while others want the first "real" bit of >> content. If epub.cover.linear is non-zero, the cover file will be >> marked as the first file to open (in the linear reading order of the >> OPF spine). More on the best practices around covers here: >> http://blog.threepress.org/2009/11/20/best-practices-in-epub-cover-images/ >> >>> ade.extensions ? (Adobe digital editions?) >> >> Yes, Adobe Digital Editions, but unused at this time. >> >> >>> Also, mobipocket requires a TOC in the main body but epub does not. if >>> I want to suppress the TOC in the main body (while leaving the ebook >>> reading software to construct it from the content.opf file) how would >>> I do this? >> >> One technique for getting around this problem is described here: >> http://blog.threepress.org/2010/11/16/better-single-source-mobiepub-files/ >> ..that said, many folks generate a "real" EPUB and a highly degraded >> one for Mobi conversion. >> > > > > -- > Robert Nagle > 12777 Ashford Point Dr #1417 > Houston, Texas 77082 > 713 893 3424 > http://www.robertnagle.info > > --------------------------------------------------------------------- > To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]