View Single Post
Old 05-06-2015, 10:36 AM   #11
roger64
Wizard
roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.
 
Posts: 2,624
Karma: 3120635
Join Date: Jan 2009
Device: Kindle PW3 (wifi)
Quote:
Originally Posted by kovidgoyal View Post
As I have said before, you do not need doctypes in your ebooks. They serve no useful purpose. That remains just as true for EPUB 3 as it is for EPUB 2. The HTML standard has moved away from DTD (A DTD is what a doctype declares). As such I have no intentions of supporting doctype in calibre, regardless of versions of epub.
Thanks for your reply.

@eschwartz
Quote:
its not like EPUB3 treats them differently than EPUB2
I just asked this question because we do not speak about the same DOCTYPE for EPUB2 and EPUB3.
Code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
is not the same as:
Code:
<!DOCTYPE html>
If I am not wrong,
- with the first (old) one, you can use named entities.
- with the second (new - html5), you can't.

But don't worry, I understand that the Calibre way will just stay the same.

Last edited by roger64; 05-06-2015 at 10:39 AM.
roger64 is offline   Reply With Quote