Quote:
Originally Posted by eschwartz
This thread, on the other hand, is a bikeshed.
Suitable only for stopping by for the sheer fun of arguing.
|
Quote:
Originally Posted by Hitch
[...]
I really really officially give up on this thread, kids. I think it's reached my head-banging limits.
Hitch
|
Quote:
Originally Posted by Hitch
Ah-hah. After reading through this whole thing, again (about colophon, I mean), the light begins to dawn, overall. To answer you, though, Tox:
|
I knew you wouldn't be able to control yourself.
Quote:
[...]
This also explains why he's so enamored of such a rigid format. His rigidity is about the OCD-ness of qualifying this and that, so you can sort it, find it, etc. He doesn't really give two hoots about whether or not a chapter is called "chapter" in XML, or not, in XHTML. He's right--for his purposes, XML would, for the categorization of his completed/purchased books, be better. It is, after all, essentially a database for text-based data.
So, to create a database of his books, like in the Calibre Catalogue, he'd likely be better off with an XML list, of those books. (Is this a good point to mention that you can export an XML Catalogue list from Calibre?) XML formatting for his list--not XML formatting for the books themselves.
He's simply wrong about his issue being the format. BUT, you can tell from his posts--and his issue--that he's not the kind of guy that's going to change his mind. 
I'm sticking with my penultimate post, however. XML is for machines, and HTML is for humans. Period.
Hitch
|
Well, yes -- XML would do a lot to solve his problems (I think, because I still can't be positive I know what the root of the complaint is
that's what you get for not being straightforward about what's really bothering you). If he would accept reformulating his mental approach.
Now, is this also a good place to point out calibre can store arbitrarily defined custom columns with whatever schema purpose one desires?