Quote:
Originally Posted by eschwartz
Create a custom column in calibre, and enter the names of translators and illustrators in their own fields.
|
End user should not do metadata hunt for himself. It should not rely on 3rd party utilities to keep his own databases. The book he gets from the store must be functionally complete by its own.
Quote:
|
EPUB can still include private, namespaced metadata.
|
Custom metadata are useless if they are not standard. If DC was not adequate, the spec authors should have created the additional dictionaries.
Quote:
|
(X)HTML/CSS already have a working system that they know how to use, which accomplishes what's needed.
|
A specific format allows to do that and more in a fraction of effort. Instead of designing and re-using stylesheets for every book... you can focus on design, not on stupid technicalities and 'layout tweaking'. It's a pure profit.
Quote:
|
the people who would use automatic conversions anyway
|
Conversion is only the first step to the book. Than you can point to things, and say, 'it's a letter salutations', 'it's a chapter number', 'it is a footnote', instead of making up stylesheet classes for paragraphs. Much simpler, isn't it?
Quote:
|
Well, you can certainly expect fonts, which is what Hitch was talking about.
|
AFAIK Kindle guidelines prohibit setting fonts for body text for customization and accessibility reasons. You don't need fancy fonts in E-book. Not all readers support embedded fonts. No one stop you from assigning font to "chapter>title label" in the exact same way you assign it to "p.chapter_no_2a". The difference is you don't know what you will get if you didn't do it in HTML; with a specific format, the user will have a nice, reasonable default from his reader+user stylesheets.
Quote:
|
Might I add that man pages aren't even written in HTML? They're written in groff.
|
HTML was intended to eventually replace TROFF.