emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Olaf Dietsche <olaf+list.orgmode@olafdietsche.de>
To: Alan L Tyree <alantyree@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: ePub construction
Date: Wed, 14 Dec 2011 09:53:35 +0100	[thread overview]
Message-ID: <87fwgn3568.fsf@rat.lan> (raw)
In-Reply-To: 1323832442.2949.1@misty

Alan L Tyree <alantyree@gmail.com> writes:

> On 14/12/11 12:42:38, Nick Dokos wrote:
>> 
>> Interesting - I downloaded the epub validator, ran Calibre on a silly
>> little org-produced HTML file and duplicated your "lang" problem.
>> 
>> AFAICT, all of the problems you mention above are legal HTML4, so
>> either
>> the epub spec (which I have not looked at: do you have a pointer?) is
>> made to trip people up by enforcing restrictions that they dreamed 
>> up,
>> or the validator is not quite as smart as it should be.
>
> Yes, the org export file validates at w3c as a valid XHTML1.0 file. The 
> ePub spec is here: http://idpf.org/epub but I admit fatigue in trying 
> to wade through it, so I don't know what XHTML1.0 constructions it 
> objects to. It seems like the kind of document that nobody has ever 
> read: sort of like EULAs and express warranties.

I took a quick look through
<http://idpf.org/epub/20/spec/OPS_2.0.1_draft.htm> and right to the
beginning <http://idpf.org/epub/20/spec/OPS_2.0.1_draft.htm#Section1.3>
"1.3: Relationship to Other Specifications" it says:

"This specification combines subsets and applications of other
specifications."

Next, in <http://idpf.org/epub/20/spec/OPS_2.0.1_draft.htm#Section1.3.4>
"1.3.4: Relationship to XHTML and DTBook" it talks about

"..., the Preferred Vocabularies do not include all XHTML 1.1 elements
and attributes."

So, even if you have a valid XHTML file, only a subset of it might be
valid for an epub book. Same goes for CSS.

Lazy as I am, I haven't looked through the other epub parts, since this
seems not relevant here.

Another interesting epub checker might be
<http://code.google.com/p/epubcheck/>, which uses "... schemas that were
developed by IDPF and DAISY. ..." according to their website.

Regards, Olaf

  reply	other threads:[~2011-12-14  8:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 22:45 ePub construction Alan L Tyree
2011-12-14  1:42 ` Nick Dokos
2011-12-14  3:14   ` Alan L Tyree
2011-12-14  8:53     ` Olaf Dietsche [this message]
2011-12-14 13:58       ` Nick Dokos
2011-12-14 23:24 ` suvayu ali
2011-12-14 23:56   ` Alan L Tyree

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87fwgn3568.fsf@rat.lan \
    --to=olaf+list.orgmode@olafdietsche.de \
    --cc=alantyree@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).