ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Thangalin <thangalin@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: EPUB XHTML Format
Date: Tue, 3 Sep 2013 18:19:38 -0700	[thread overview]
Message-ID: <CAANrE7r9OaMc65SaiJYhZ8x3=GtrQzYRrmZrfiLvcHiuot=xJA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1241 bytes --]

Hi,

The attached t.tex file produces the attached t.xhtml file. I have looked
at the following documents:

   - http://en.wikipedia.org/wiki/EPUB#Open_Publication_Structure_2.0.1
   - http://en.wikipedia.org/wiki/DTBook
   - http://www.idpf.org/epub/20/spec/OPS_2.0.1_draft.htm
   - http://www.w3.org/TR/xhtml11/doctype.html
   - http://www.w3.org/TR/html5/sections.html

It seems that the macros in t.tex are being written out as XML elements,
verbatim. It is my understanding that these XML elements, however, do not
conform to the minimal content models associated with XHTML 1.1.

What needs to happen to take a minimal ConTeXt file (such as the attached)
to produce a minimum viable EPUB that:

   - Generates XHTML headers (including <!DOCTYPE and <html...>)
   - Produces images as img tags, rather than float tags.
   - Uses typical XHTML tags for <body> elements (e.g., <ol> for ordered
   lists).

Ideally, I would like to do something such as:

   - context t.tex
   - mtxrun --script epub --make t.specification

to generate an EPUB that passes validation of
epubcheck<http://code.google.com/p/epubcheck/wiki/Library>,
with an output XHTML file that more closely matches the XHTML specification.

How can I help?

Kind regards.

[-- Attachment #1.2: Type: text/html, Size: 1807 bytes --]

[-- Attachment #2: t.tex --]
[-- Type: application/x-tex, Size: 995 bytes --]

[-- Attachment #3: t.xhtml --]
[-- Type: application/xhtml+xml, Size: 3036 bytes --]

[-- Attachment #4: epub-errors.log --]
[-- Type: application/octet-stream, Size: 1647 bytes --]

Epubcheck Version 3.0.1

Validating against EPUB version 2.0
ERROR: t.tree/t.epub/OEBPS/t.opf(18,82): value of attribute "id" is invalid; must be an XML name without colons
WARNING: t.tree/t.epub/OEBPS/toc.ncx: meta@dtb:uid content 'BookId' should conform to unique-identifier in content.opf: 'urn:uuid:26204a45-4754-ab8c-067d-97c51c130f64'
ERROR: t.tree/t.epub/OEBPS/t.xhtml(9,202): elements from namespace "" are not allowed
ERROR: t.tree/t.epub/OEBPS/t.xhtml(12,26): element "xhtml:a" not allowed here; expected element "xhtml:html"
ERROR: t.tree/t.epub/OEBPS/t.xhtml(12,26): attribute "name" not allowed here; expected attribute "accesskey", "charset", "class", "coords", "dir", "href", "hreflang", "id", "lang", "rel", "rev", "shape", "style", "tabindex", "target", "title", "type" or "xml:lang"
ERROR: t.tree/t.epub/OEBPS/t.xhtml(12,87): elements from namespace "" are not allowed
ERROR: t.tree/t.epub/OEBPS/t.xhtml(36,27): element "xhtml:a" not allowed here; expected element "xhtml:html"
ERROR: t.tree/t.epub/OEBPS/t.xhtml(36,27): attribute "name" not allowed here; expected attribute "accesskey", "charset", "class", "coords", "dir", "href", "hreflang", "id", "lang", "rel", "rev", "shape", "style", "tabindex", "target", "title", "type" or "xml:lang"
ERROR: t.tree/t.epub/OEBPS/t.xhtml(36,94): elements from namespace "" are not allowed
ERROR: t.tree/t.epub/OEBPS/t.xhtml(40,98): elements from namespace "" are not allowed
ERROR: t.tree/t.epub/OEBPS/t.xhtml(44,75): elements from namespace "" are not allowed
ERROR: t.tree/t.epub/OEBPS/t.xhtml(47,107): elements from namespace "" are not allowed

Check finished with warnings or errors


[-- Attachment #5: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2013-09-04  1:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04  1:19 Thangalin [this message]
2013-09-04  9:20 ` Hans Hagen
2013-09-04 17:55   ` Thangalin
2013-09-05 13:55     ` Hans Hagen
2013-09-12 14:32       ` Alan BRASLAU
2013-09-05 16:38   ` Hans Hagen
2013-09-05 16:57     ` Thangalin
2013-09-05 17:57       ` Khaled Hosny
2013-09-05 18:22         ` Hans Hagen
2013-09-05 17:22     ` Aditya Mahajan
2013-09-05 18:21       ` Hans Hagen
2013-09-05 18:11 ` honyk
     [not found] ` <00b501ceaa63$61805e50$24811af0$@tosovsky@email.cz>
2013-09-05 18:20   ` Aditya Mahajan
2013-09-05 18:24     ` Hans Hagen
2013-09-05 19:54       ` Mica Semrick
2013-09-05 21:15       ` Michael Hallgren
2013-09-05 22:00     ` Thangalin
2013-09-06 16:09       ` Hans Hagen
2013-09-06 16:36       ` Mica Semrick
2013-09-06 20:20         ` Thangalin
2013-09-06 21:22           ` Thangalin
2013-09-06 21:27             ` Aditya Mahajan
2013-09-07 12:07           ` Hans Hagen
2013-09-07 18:31             ` Thangalin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAANrE7r9OaMc65SaiJYhZ8x3=GtrQzYRrmZrfiLvcHiuot=xJA@mail.gmail.com' \
    --to=thangalin@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).