MobileRead Forums - View Single Post

fdwojo · 11-08-2019, 07:24 PM

Hello there, everybody. I've occasionally looked to these forums for my SIGIL and CALIBRE information searches, and been impressed each time.

As many Sigil users know, they dropped the BookView feature in it. Fortunately, for those of us who liked to see the WYSIWYG aspect, we know have PageEdit to help ourselves out.

My question is:

The description of PageEdit says it is an "ePub XHTML Visual Editor". Granted, I've used PageEdit with purely HTML ebooks. In fact, when I edit my EPUBs, I tend to change all text files to either HTML or CSS. If I see an XHTML, I generally rename it to HTML.

As such, I'm wondering whether (with respect to ebooks only) what value do XHTML files have over HTML files? Is there something I can do in an ebook with XHTML that I can't with HTML? I can easily image that for a website, XHTML might have some pretty nifty features. But for an ebook, is there *ANY* feature that XHTML has that can benefit me in an ebook?

If it helps, I (almost) exclusively use Sigil to compile and edit FanFiction stories (from websites like fanfiction_net) into a final, more pleasing aspect. Like many of you, I like having my ebooks as perfect and proper as possible.

Thus, is there any reason (for ebooks) to use XHTML? Or am I safe in making all my XHTML files into HTML and reading my ebooks in that way?

Thanks for any comments.

Frank

P.S. Is EPUB 2.0 good enough for the long haul, or will EPUB 3.0 have features that become a dealbreaker? Specifically, it seems that all the ebook readers are quite content to stay at EPUB 2.0 compatibility and EPUB editors seem to not dissuade users from creating EPUB 2.0 documents.

11-08-2019, 07:24 PM	#1
fdwojo Member Posts: 23 Karma: 10 Join Date: Jun 2012 Device: Samsung Note20 Ultra, Kindle Fire HD10	Is there any value to XHTML vs HTML? Hello there, everybody. I've occasionally looked to these forums for my SIGIL and CALIBRE information searches, and been impressed each time. As many Sigil users know, they dropped the BookView feature in it. Fortunately, for those of us who liked to see the WYSIWYG aspect, we know have PageEdit to help ourselves out. My question is: The description of PageEdit says it is an "ePub XHTML Visual Editor". Granted, I've used PageEdit with purely HTML ebooks. In fact, when I edit my EPUBs, I tend to change all text files to either HTML or CSS. If I see an XHTML, I generally rename it to HTML. As such, I'm wondering whether (with respect to ebooks only) what value do XHTML files have over HTML files? Is there something I can do in an ebook with XHTML that I can't with HTML? I can easily image that for a website, XHTML might have some pretty nifty features. But for an ebook, is there ANY feature that XHTML has that can benefit me in an ebook? If it helps, I (almost) exclusively use Sigil to compile and edit FanFiction stories (from websites like fanfiction_net) into a final, more pleasing aspect. Like many of you, I like having my ebooks as perfect and proper as possible. Thus, is there any reason (for ebooks) to use XHTML? Or am I safe in making all my XHTML files into HTML and reading my ebooks in that way? Thanks for any comments. Frank P.S. Is EPUB 2.0 good enough for the long haul, or will EPUB 3.0 have features that become a dealbreaker? Specifically, it seems that all the ebook readers are quite content to stay at EPUB 2.0 compatibility and EPUB editors seem to not dissuade users from creating EPUB 2.0 documents.