Bug 141664 - Epub export does not validate
Summary: Epub export does not validate
Status: RESOLVED DUPLICATE of bug 144778
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.0.3.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 141187
  Show dependency treegraph
 
Reported: 2021-04-13 01:27 UTC by Lee Higbie
Modified: 2021-10-13 13:09 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Test file for creaton of an epub exported file followed by screen shots for 3 validators analysis.. (242.78 KB, application/vnd.oasis.opendocument.text)
2021-04-13 01:27 UTC, Lee Higbie
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lee Higbie 2021-04-13 01:27:42 UTC
Created attachment 171140 [details]
Test file for creaton of an epub exported file followed by screen shots for 3 validators analysis..

Exporting to .epub format does not pass validation tests.  The errors look minor, but the result renders the .epub output file unacceptable to many of the major e-book vendors.  One reason the bug is severe is that the validators often describe problems in a form that only the converter-writer could comprehend (see the last example in the attachment, for example).

The first attached file shows the test code.  The second one shows the results of three of validators' analyses.  

The second attachment starts with the test file text and a description of how the .epub file was created.  This is followed by the name or URL of each validator and a screenshot of the resulting analysis.
Comment 1 Aleksandra 2021-08-11 15:33:46 UTC
Also in

Version: 7.1.4.2 / LibreOffice Community
Build ID: a529a4fab45b75fefc5b6226684193eb000654f6
CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx
Locale: en-GB (en_GB.UTF-8); UI: en-US
Calc: threaded
Comment 2 Michael Warner 2021-10-13 13:09:47 UTC

*** This bug has been marked as a duplicate of bug 144778 ***