Quote:
Originally Posted by Sarmat89
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.
Custom metadata are useless if they are not standard. If DC was not adequate, the spec authors should have created the additional dictionaries.
|
So go complain to the Dublin Core committee, but what does that have to do with EPUB?
And you have no need to rely on calibre, you are free to edit the content.opf directly, or use Sigil, or calibre's Editor, or any other EPUB editor (should one exist).
Quote:
|
HTML was intended to eventually replace TROFF.
|
Oh yeah?
As Hitch said, so was DocBook.
Anyway, groff can output HTML... amongst several other target formats. But I think using HTML as the original source is pretty rare.
Usually people use Asciidoc, markdown, TeX, or DocBook (that again). Depending on whether they want to write it the easy way or the finely-controlled way.
(This becomes possible by having a very rigid standard and not deviating from it. But manpages are supposed to conform, not do interesting things...)
Well, anything under the umbrella of the GNU would much rather you read their own Texinfo documentation. But even they don't expect you to open up a browser first.
But first you say HTML was designed as a replacement for groff/troff, then you back down (?) and say it was merely intended to be used as a replacement.
Since groff/troff is still around and in use, going on 50 years later, I'd venture to say that there is something wrong with your conclusion, at the least.
Whether or not HTML once had any sort of informal or formal relationship to groff is irrelevant.
Because HTML has come a long way, and I certainly cannot fathom how you could argue NOW that it is "suitable only for writing man pages".