Patrice Dumas <pertu...@free.fr> writes: > Hello, > > On Tue, Aug 20, 2024 at 09:23:57AM +0100, Daniel Cerqueira wrote: >> The EPUB file is produced without any errors, and when I check to see if >> the file is valid (using the `epubcheck` program) I get this 2 errors: > > My current view on EPUB conformance is that seems to be important to > have full conformance in some cases (as Daniel reported) and even if I > think that having such a level of conformance is pointless or even > wrong, I also think that it is important to provide a possibility of > full epubcheck conformity, even if it is not the default. For the > release, however, I think that it is too late. > > Here is my proposal: > > 1) for the release, we do not make any change to the code, but we > document that the EPUB we produce is no conformant. We ship Daniel > patches in contrib/ and we document that they exist too. > > 2) after the release we fix conformance issues as we can/want, for > instance use CSS for border, add meta data for a publication date. I am > pretty sure there were other issues. If there are still conformance > issues and we do not want to change the default HTML output, we add a > customization variable for epubcheck strict conformity and add the > corresponding code. > > Does it look ok?
This seems like a progress to me. Regarding having other issues, the dcterms:modified and the border of the index table element, were the only issues that I encountered when producing an EPUB file from my book's Texi file. Book writers should be able to use Texinfo, without this causing any friction.
signature.asc
Description: PGP signature
