[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: texi to epub

From: Patrice Dumas
Subject: Re: texi to epub
Date: Sat, 18 Dec 2021 22:01:53 +0100

On Sat, Dec 18, 2021 at 08:43:23AM -0800, Per Bothner wrote:
> On 12/18/21 07:38, Patrice Dumas wrote:
> > The idea is that it would be set if doing XHTML 1.1, be it for epub or
> > as an output, as it is a prerequisite for epub if I understood right.
> > 
> > For now, my plan is to do XHTML1.1 as a separate init file.
> Why? XHTML 1.1 is an obsolete format.  It is not required for EPUB 3.x,
> which is a 10-year old specification.
> EPUB does requires content document to be XML:
> http://idpf.org/epub/30/spec/epub30-contentdocs.html#sec-xhtml

It seems that it does not change the work required compared to XHTML 1.1
which is to have a correct XML document.  Something I cannot find,
however, is what to put at the beginning to be able to check validity
of the resulting document if it is HTML5 XML.  Can you please tell me?

> However, my reading of the spec finds no indications that custom data 
> attributes are
> disallowed.  It notes that data attributes must be stripped before being fed
> to a validator - which implies that they are allowed, but the validator does 
> not handle them:
> http://idpf.org/epub/30/spec/epub30-contentdocs.html#app-xhtml-schema
> So my recommendation is: Just leave the data attributes in, even for 

If it prevents validation, it is better to be able to set it on and off.

> I think my previous poposal is still reasonable:
> https://lists.gnu.org/archive/html/bug-texinfo/2021-09/msg00000.html

It seems to me that XML_OUTPUT_MODE "polyglot" would only need changing
some customization variable for the header, so I am not so convinced
that it is really interesting.

I'll do the code to generate XML, though I am still unsure whether it
should be in the HTML converter directly or as an init file.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]