conversion to .odt

[r728626]

I have to convert to .docx, then open it on libreoffice, and only then, save as .odt

The output is two files, and I still have to delete the original .docx because calibre can't convert them directly.
Since it's a very accessible format, and open source, unlike .docx, it's very important that calibre converts to .odt.

I believe it even isn't that difficult, if not some plugin may automate the process for an immediate convenience.

[Bookstooge]

Well, since odt is open source and calibre is open source and you say yourself that it shouldn't be difficult, I look forward to your plugin you are going create, or even a forked version of calibre.

[r728626]

Now I know this forum isn't for suggestions.

But at least is a place for autists like yourself.

[BetterRed]

@r728626 - I found two previous requests for an ODT output feature one in 2013, and this one in Feb 2018 ==>> .odt Output Option?

Given the paucity of requests & a simple workaround (convert to DOCX, open & save in Open Office) I can't see why one would regard an ODT Output feature as 'very important'.

BR

[itimpi]

Calibre CAN convert .docx files so I do not know why the OP needs the conversion to .odt.

[DNSB]

Originally Posted by itimpi

Calibre CAN convert .docx files so I do not know why the OP needs the conversion to .odt.

From reading through the thread, it appears that he wants calibre to convert docx directly to odt. I am wondering what he is reading the odt files on that makes it a preferred format or why simply opening the docx file in LibreOffice and then saving as odt is not working for him.

Since the OP mentions opening docx files with LibreOffice and then saving as odt, I find it hard to agree that it is "very important" that calibre add odt as an output format.

[Fiat_Lux]

Originally Posted by DNSB

From reading through the thread, it appears that he wants Calibre to convert docx directly to odt. I am wondering what he is reading the odt files on that makes it a preferred format or why simply opening the docx file in LibreOffice and then saving as odt is not working for him.

Since the OP mentions opening docx files with LibreOffice and then saving as odt, I find it hard to agree that it is "very important" that calibre add odt as an output format.

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.

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

[DNSB]

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?

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.

[BetterRed]

@DNSB - I don't think the OP wanted to convert DOCX to ODT, I think his issue was that the 'best' way to get something that Writer can edit is to convert what you have (epub, mobi, pdf etc) to DOCX. His objection to doing that was that the DOCX format is not a standards based format.

BR

[DNSB]

Originally Posted by BetterRed

@DNSB - I don't think the OP wanted to convert DOCX to ODT, I think his issue was that the 'best' way to get something that Writer can edit is to convert what you have (epub, mobi, pdf etc) to DOCX. His objection to doing that was that the DOCX format is not a standards based format.

You're right. I mis-read what he was trying to do.

If he really objects to docx on the grounds that it is not open source, he could always export as RTF. My personal opinion is that since docx is a zip wrapper around a collection of Office Open XML files, arguing that odt is better since it is open source is not going to fly.

As for the argument from @Fiat Lux that calibre should support the ISO/IEC 26300-3:2015 standard but not the ISO/IEC 29500-1:2016 standard claiming that ISO/IEC 29500-1:2016 is "a standard for legacy documents, and as such, usage for non-legacy documents is highly discouraged". Oddly the ISO document, part 4 (Transitional Migration Features) does discuss legacy markup for transitional documents. Otherwise, I could find no mention that ISO/IEC 29500-1:2016 is for legacy documents. There was quite a bit of discussion around whether 29500 was really required when 26300 covered much the same territory however duplication of effort when it comes to standards is close to a hallmark of the International Organization for Standardization and the International Electrotechnical Commission. Just look at the ISO/IEC 29166 document covering translation between ISO/IEC 26300 and ISO/IEC 29500 document formats.

[BetterRed]

Originally Posted by DNSB

You're right. I mis-read what he was trying to do.

Originally Posted by DNSB

As for the argument from @Fiat Lux that calibre should support the ISO/IEC 26300-3:2015 standard but not the ISO/IEC 29500-1:2016 standard claiming that ISO/IEC 29500-1:2016 is "a standard for legacy documents, and as such, usage for non-legacy documents is highly discouraged". Oddly the ISO document, part 4 (Transitional Migration Features) does discuss legacy markup for transitional documents. Otherwise, I could find no mention that ISO/IEC 29500-1:2016 is for legacy documents. There was quite a bit of discussion around whether 29500 was really required when 26300 covered much the same territory however duplication of effort when it comes to standards is close to a hallmark of the International Organization for Standardization and the International Electrotechnical Commission. Just look at the ISO/IEC 29166 document covering translation between ISO/IEC 26300 and ISO/IEC 29500 document formats.

I treat that sort of gobbledegook with the same disdain as the Prince did of his uncle's drunken revelry:

But to my mind, though I am native here
And to the manner born, it is a custom
More honor’d in the breach than the observance.

BR

[Quoth]

Originally Posted by DNSB

From reading through the thread, it appears that he wants calibre to convert docx directly to odt. I am wondering what he is reading the odt files on that makes it a preferred format or why simply opening the docx file in LibreOffice and then saving as odt is not working for him.

Since the OP mentions opening docx files with LibreOffice and then saving as odt, I find it hard to agree that it is "very important" that calibre add odt as an output format.

Opening docx in LibreOffice and SaveAs odt.


Or for ARBITRARY conversion of eBook to edit it:
Export as RTF from Calibre
Open in LibreOffice and SaveAs .odt (or .docx)

I've also found that if styles / page sizes go strange, using RTF works to fix (Export/Import). It seems to preserve links (internal & external) and Bookmarks/Anchors. Good if using LibreOffice or MS Office or both.

What I'd like is .odt IMPORT to Calibre to work properly. I have to SaveAs .docx for Calibre for best ebook match to odt original.
There is an issue with "graphics style" on odt to docx conversion that the margins around an image are lost.

[kovidgoyal]

docx is definitely open source, it is an ISO standard, and I in fact used the standard to develop docx suport in calibre. As for ODT, I'm really not interested given that most office suites support docx just fine, but patches are most welcome. In fact the current ODT input plugin is based on a forked and much improved version of odfpy but it is nowhere near as good as the docx plugin, because I wrote that from scratch with far more attention to detail than odfpy has.

[Quoth]

Originally Posted by kovidgoyal

docx is definitely open source, it is an ISO standard, and I in fact used the standard to develop docx suport in calibre. As for ODT, I'm really not interested given that most office suites support docx just fine, but patches are most welcome. In fact the current ODT input plugin is based on a forked and much improved version of odfpy but it is nowhere near as good as the docx plugin, because I wrote that from scratch with far more attention to detail than odfpy has.

Yes, I read on your website that docx is "best" input format and I've found that.
Unfortunately standalone MS Office seems to have no future and Windows has become a disaster (using Windows & Selling / training/install from 1991 and NT from 1994). So I entirely use Linux. I was using LibreOffice on Windows for two years before the final switch.

Unfortunately odt is far better than docx for LibreOffice editing. I'd love an odt import that works as well as docx. I have zero other use for docx as I upload epub to Amazon, PDF for POD paper and MS DOC 97-2003 format for anyone needing MS Word format. I upload Dual Mobi, epub and MS .doc formats to Smashwords, they don't take .docx and Calibre (from LibreOffice Writer via docx) does better conversion to mobi/AZW and epub than Smashwords from doc.
Amazon's output to old kindles, apps and new kindles is perfect from the Calibre created epub (from LibreOffice Writer via docx) and poor from .doc or .docx

I'm delighted with Calibre and use it to convert Kindle to epub and clean up mobi or epub from Gutenberg.

I started using it with my PW2, then a Kindle DXG on XP. Time to donate again
Excellent for the Kobo, Sony, Nook, Kindles I have and for upload to Amazon and Smashwords (thus Apple, Barnes&Noble, Kobo etc via them).

I've found rather than saving Websites and convert in Calibre, that paste/edit in LibreOffice Writer and convert docx to epub in Calibre works best. Saves lots of paper!

[JSWolf]

Originally Posted by FrustratedReader

Yes, I read on your website that docx is "best" input format and I've found that.
Unfortunately standalone MS Office seems to have no future and Windows has become a disaster (using Windows & Selling / training/install from 1991 and NT from 1994). So I entirely use Linux. I was using LibreOffice on Windows for two years before the final switch.

MS Office does indeed have a future. Windows is not a disaster. These are just your misguided opinions.