View Single Post
Old 08-09-2020, 08:21 PM   #32
roger64
Wizard
roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.roger64 ought to be getting tired of karma fortunes by now.
 
Posts: 2,625
Karma: 3120635
Join Date: Jan 2009
Device: Kindle PW3 (wifi)
Quote:
Originally Posted by philja View Post
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
Quote:
"Use first image as cover image".
2. - for odtImport, you must look at your config.xml file, and check the value of
Quote:
<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.

Last edited by roger64; 08-09-2020 at 08:50 PM. Reason: similar
roger64 is offline   Reply With Quote