[Plugin] ODTImport

[philja]

Originally Posted by roger64

Hi

As a -nearly - daily user of both writer2xhtml.oxt on LO 6.4.5.2. and of writer2latex.jar with Sigil 1.3. and odtImport plugin 0.3.1. (both of them use in fact writer2xhtml 1.6.1.), I just can say that they both work nicely today. I'll try it asap with LO 7.

I'm interested that you get writer2xhtml to run well with LO 6.4.5.2. I'm using 6.3.5.2 and I couldn't get any of the writer2xhtml options to run to completion when launched from the File > Export menu. Every time the export failed with some sort of general import/export error.

This was disappointing because I rather liked the gui interface with all the options that writer2xhtml presented.

The one case which did work ok was from the Publish button on writer2xhtml's small toolbar. Because it didn't allow me to select a file name, care was needed to avoid overwriting a previous version.

- Images in the odt file (including cover) are processed without problem.

In the case I tried, I didn't have a cover image in the odt file because I normally use Sigil to add it to the epub file. So I was somewhat surprised to see that the ODTimport plugin hijacked my first image to build a cover page - especially since it didn't reuse the image in its proper place.

Over the weekend, I loaded an odt file into Calibre and then converted it to epub. The result wasn't too bad but the epub did need some cleaning up.

Perhaps the worst was Calibre's production of unwanted and useless <span>'s. One short paragraph was more than doubled in size by what seemed to me to be useless <span>'s calling up CSS "classes" to apply to a single letter. The original odt paragraph was a two liner in Text Body style with no manual formatting applied.

Calibre did not hijack any image to produce a cover page but instead created the page with a text based svg image.

At present, I'm unable to decide which workflow is going to require the least cleaning up.

[roger64]

Originally Posted by philja

In the case I tried, I didn't have a cover image in the odt file because I normally use Sigil to add it to the epub file. So I was somewhat surprised to see that the ODTimport plugin hijacked my first image to build a cover page - especially since it didn't reuse the image in its proper place.
.

Hi.

There is no "hijacking" in writer2xhtml but only user selected options.
1. - for the writer2xhtml GUI (for LO) you have to check or uncheck this one

"Use first image as cover image".

2. - for odtImport, you must look at your config.xml file, and check the value of

<option name="cover_image" value="true" />

and set it according to your need.

As you can see, the wording of the config.xml options can be slightly different from the one of the GUI, but if you go carefully and slowly through all the options of the config.xml , you'll find similar ones to the GUI.

The purpose of each option is given in the writer2xhtml documentation online.

[philja]

Originally Posted by roger64

Hi.

2. - for odtImport, you must look at your config.xml file, and check the value of

and set it according to your need.

As you can see, the wording of the config.xml options can be slightly different from the one of the GUI, but if you go carefully and slowly through all the options of the config.xml , you'll find similar ones to the GUI.

The purpose of each option is given in the writer2xhtml documentation online.

Thanks for that, Roger. Complete ignorance on my part. I had not even investigated under the hood on the ODTimport plugin.

I see I've got some reading up to do to optimise my settings for the plugin. And I should think that once I've taken that step, it will probably be as easy as the LO Writer Extension.

[roger64]

Originally Posted by philja

I see I've got some reading up to do to optimise my settings for the plugin. And I should think that once I've taken that step, it will probably be as easy as the LO Writer Extension.

You're welcome.

Yes, it's worth it if you plan to use odtImport regularly. You need to do it only once.
The same goes for the epub.css file (if you wish to append one).

[Leonatus]

Windows 10 32 bit, Sigil v. 1.4.3.
I used the plugin for the first time, but got the following error message:

Status: failed


This is Writer2xhtml, Version 1.4 (2014-02-16)

Starting conversion...
Reading style sheet C:\Users\Juerg\AppData\Local\sigil-ebook\sigil\plugins\ODTImport\epub.css
Reading configuration file C:\Users\Juerg\AppData\Local\sigil-ebook\sigil\plugins\ODTImport\config.xml
Converting C:\Users\Juerg\OneDrive\OCR\Johann K. Musus, Die Entfhrung\Johann K. Musus, Die Entfhrung.odt
Done!

I only can see that the original file location should be named: "Musäus", instead of "Musus". Could this be the reason for the failure?

[Doitsu]

Originally Posted by Leonatus

Windows 10 32 bit, Sigil v. 1.4.3.
I used the plugin for the first time, but got the following error message:
[CODE]Status: failed

You most likely installed the wrong version of the plugin. Please check the plugin version in the Plugin Manager dialog box.

It should show ODTImport 0.3.2.

If it doesn't, please uninstall the current version and install ODTImport 0.3.2.

[Leonatus]

You are right, thank you! But now it's this message:

Status: failed

Python Version: 3.8.3 

writer2latex.jar command line:
java -jar C:\Users\Juerg\AppData\Local\sigil-ebook\sigil\plugins\ODTImport\writer2latex.jar -epub -config=C:\Users\Juerg\AppData\Local\sigil-ebook\sigil\plugins\ODTImport\config.xml -stylesheet=C:\Users\Juerg\AppData\Local\sigil-ebook\sigil\plugins\ODTImport\epub.css E:/OCR/Johann Musus, Die Entfuhrung/Johann K. Musäus, Die Entführung.odt

writer2latex.jar messages:

This is Writer2xhtml, Version 1.6 (2018-03-06)

Starting conversion...
Reading style sheet C:\Users\Juerg\AppData\Local\sigil-ebook\sigil\plugins\ODTImport\epub.css
Reading configuration file C:\Users\Juerg\AppData\Local\sigil-ebook\sigil\plugins\ODTImport\config.xml
Converting E:\OCR\Johann Musus, Die Entfuhrung\Johann K. Musus, Die Entfhrung.odt
Done!

[Doitsu]

Originally Posted by Leonatus

You are right, thank you! But now it's this message:[CODE]Status: failed

Unfortunately, I can't reproduce this issue on my Windows 10 machine, even if I insert spaces and umlauts into the .odt file name.

If you've installed this plugin on an older Windows machine without Unicode support, try removing all umlauts and/or accented characters from the file name.

If that doesn't fix your problem, test the plugin with this test file, which converted fine on my Windows 10 machine.

[Leonatus]

Renaming the file (and the directory, for safety reasons) and removing all Umlauts and periods did the trick!
The result looks really pretty.
Thank you!