Quote:
Originally Posted by ProDigit
Thanks for explaining so far!
I can't help but think that epub code is far from optimized, much like how MS office creates HTML pages, with lots of things that aren't really necessary.
|
No, not really. All things are necessary. In essence you need the file structure (folders not required), the mimetype, the opf and ncx and one or more XHTML files.
Quote:
Originally Posted by ProDigit
Suppose I just want to display my book, do titles in bold and larger letter type than the regular text; but I don't really care about what lettertype or fontsize it will be,
can I get rid of CSS, and just simply compress HTML files in an epub?
|
You don't NEED CSS, it only makes it easier, better structured and maintainable. If you are fine with the standard layout interpretation of the reader, you don't need it. Also, don't put stuff in you stylesheet you don't need. Keep it simple.
Quote:
Originally Posted by ProDigit
Suppose I don't want an ID reference number, and I don't want external sites within my ebook,
What would be an utmost minimalistic epub (eg: one with no extra lines of code, one that just displays a cover photo, a toc, and one or two chapters)?
|
Certain things are required. An unique UID, the files mentioned earlier and some metadata. The title, author and language are mandatory. I would say you need one HTML for the cover, a TOC is included if you maintain your toc.ncx file correctly and a HTML for each chapter.
Quote:
Originally Posted by ProDigit
Most of the manuals online add too much data in their epub. Data that I find is not really necessary. Like for those people that load their books from a file browser structure, adding a title within an epub book more than once is not really necessary.
In fact, I see no reason to write a book title within an epub, if it's already mentioned in the filename.
|
The title tag within a HMTL is not used. The tag must be there (part of the XHTML spec), but does not to be filled in. The title metadata in the OPF is required by the ePUB specs.
Frankly, what you think is important but if it is part of the requirements of the specs, you need it anyway.
Quote:
Originally Posted by ProDigit
From point of writing a very minimalistic epub, I find that the epub format has way too much garbage in it, that is unneccessary for any user to read.
It may be good for having databases, and organizing stuff automatically, or converting books, but to read, all you need is a basic HTML0 book, I'd presume?
|
What do you consider to be garbage? Can you give examples? Metadata is hardly garbage, as it is helpful to identify a book. Remember, readers don't use filenames but the filenames. If you don't want all that, don't create an ePUB, but a HTML book.
Again, read about the format on the Jedisaber site. It describes all the really required files.