Quote:
Originally Posted by Fiat_Lux
When converting from one file format to another, the tool that was used leaves artifacts behind. Artifacts that build up, and create a layer of cruft that affects the quality of the presentation format of the document. It is not uncommon for format conversions to have a negative impact on the structural markup of the document. A direct conversion from format x to ODT, from within Calibre would reduce cruft buildup, and be a more faithful representation of the original document.
|
An interesting claim. Do you have any evidence that a conversion from docx to odt in calibre would actually be a "more faithful representation of the original document" than using LibreOffice for which odt is a native format? You did notice the OP wanted calibre to convert a docx input file to an odt output file?
Quote:
Originally Posted by Fiat_Lux
ODF Toolkit ( https://odftoolkit.org/) is a Java library for creating ODF format documents. ODFPy ( https://github.com/eea/odfpy) is a python library for creating ODF format documents.
ISO/IEC 29500 is a standard for legacy documents, and as such, usage for non-legacy documents is highly discouraged. (It is a technical violation of ISO 9000 to use ISO 29500 file formats for non-legacy documents.) Thus, there is no legitimate reason for Calibre to support ISO/IEC 29500, but there is a legitimate reason for Calibre to support ISO/IEC 26300 |
Considering that calibre is intended for handling ebook files for reading on an ereader either dedicated or ereader application, why would supporting document file conversion to a document file format that is not used by an ereader be considered a legitimate reason?
Are you volunteering to create a plugin for calibre to handle conversions
to odt format? Though as far as I can tell, the sheer number of potential calibre users wanting to convert their current ebook formats to odt is, to put it gently, underwhelming.