Few automated HTML tools generate it, and the changes
from XHTML 1.0 are simply annoying rather than useful.
All Publication Resources referenced
from an XHTML Content Document must conform to the constraints for Publication Resources defined in EPUB Publication — Content Conformance [Publications30]
Publication Resources referenced
from XHTML and SVG Content Documents and CSS must now be Core Media Types unless referenced in a context that provides native intrinsic fallback capabilities.
Not exact matches
Aside
from Evernote, all of the above involve direct publishing online or the apps publish to the blog using
xhtml protocol, usually with a touch / tap of a button.
If you're working
from InDesign CS3, when InDesign creates an epub's
XHTML, it tags every paragraph with the
tag.
Use http://word2cleanhtml.com to convert text
from your Word doc to well - formatted HTML /
XHTML code.
Open each
XHTML file (s) and change your headings» tags
from tags to standard HTML heading tags:
It also helps with conversion tools for amazons proprietary ebook formats
from a maelstrom of other formats, including, xml, html, epub, to the feed format Amazon demands which is NITF,
XHTML and RSS formats.
This is a strategy I've been advocating for some time; in fact, I'm doing a workshop on this subject, «Upfront
XHTML,» at O'Reilly TOC in February, where I'll provide examples of publishers ranging
from Hachette to the World Bank to the University of Toronto Press to Harvard Business Publishing that are using this strategy.
The transformation
from TEI to HTML is not that different
from transforming to ePub, which is basically
XHTML in a zip container, and the required metadata is all available in the TEI header.
Note that this method of retrieving content dimensions only applies when bitmap images are referenced directly
from the spine (i.e. not embedded in
XHTML or SVG Content Documents).
As most of the contents of an EPUB are just what you'd find when working on a straightforward website, if you're already comfortable hand coding website assets such as
XHTML and CSS files, then creating an e-book
from scratch may be the easiest and cleanest solution.
' When producing alternative textual content for MathML markup, it should be able to dynamically generate such content
from the given Presentation MathML, and if not, must give preference to
XHTML Content Document fragments followed by the alttext attribute on the m: math element.
The
XHTML document type defined by this specification is based on W3C [HTML5], and inherits all definitions of semantics, structure and processing behaviors
from the HTML5 specification unless otherwise specified.
The initial sync of the EPUB book
from iTunes takes care of this part, allowing you to modify an individual
XHTML or CSS file using the technique described rather than having to rebundle EPUBs after edits and re-sync.
The
XHTML profile defined by this specification inherits all definitions of semantics, structure and processing behaviors
from [HTML] unless otherwise specified.
XHTML Content Documents support the embedding of SVG 1.1 document fragments by reference (embedding via reference, for example,
from an img or object element) and by inclusion (embedding via direct inclusion of the svg: svg element in the
XHTML Content Document)[SVG].
Index locators extend the suggested
XHTML context of terms
from the EPUB Structural Semantics Vocabulary [StructureVocab] to include the a element; terms
from other associated vocabularies may also be used, in accordance with Vocabulary Association [ContentDocs301] guidelines.
This section defines deviations
from, and constraints on, the underlying [HTML] document model applicable to EPUB 3.1
XHTML Content Documents.
XHTML content in EPUB follows a few rules that might be unfamiliar to you
from general Web development:
Users with EPUB readers benefit
from the additional metadata and automatic table of contents, but those without can simply treat the EPUB archive as a normal ZIP file and view the
XHTML contents in a browser.
XHTML Content Documents support the embedding of SVG document fragments by reference (embedding via reference, for example,
from an img or object element) and by inclusion (embedding via direct inclusion of the svg element in the
XHTML Content Document)[SVG].
In the case of Publications that exclusively reference
XHTML Content Documents
from their spines, the toc nav will typically correspond to the aggregation of HTML5 outlines of those documents (excluding any subtrees that do not contribute to the primary Publication outline).
You can use them for EPUB 2 compliance (SVG with
XHTML fallbacks, as SVG wasn't allowed in the spine previous), and even for script-less reading systems (fallback
from an EPUB 3 - compliant
XHTML content document marked as scripted to another EPUB 3 - compliant
XHTML content document not marked as scripted).
By default, when you set an
XHTML content document as pre-paginated, the dimensions of the page are obtained
from the viewport property in the head of the document:
It's hard to guess without seeing the file, but if you're linking
from one
xhtml document to another you probably don't have the right media type on the manifest entry for the second.
If you want to sideload documents or download them
from the Web, you can access TXT, HTML,
XHTML and RTF files.
This element exists to enable the development of specialized content identification, processing and rendering features, such as the ability to define embedded preview content, or assemble an index or dictionary
from its constituent
XHTML Content Documents.
be constructed
from text - based
XHTML or SVG Content Documents (i.e., text content is not represented as images);
The following example shows a reference to a remote audio file that has to be referenced
from the manifest (the audio is rendered inline in the
XHTML Content Document so it is a Publication Resource).
This is because UEC creates your eBooks
from the ground up and generates 100 % clean and lean
XHTML code - unlike Calibre that tries to convert a Microsoft Word document with all that junk formatting hidden characters that make your eBooks look like c ***!
Here are a couple of key paragraphs
from section 1 of «Frequently Asked Questions (FAQ) about the future of
XHTML» (W3C, July 2, 2009):