Thread: Java504 and odt
View Single Post
Old 12-22-2015, 07:47 PM   #6
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)
Hi

I correct my previous message since I have the answer by now.

To find the culprit, I had to unzip the odt file and open the content.xml file. It's not about any unexisting src tags as I -wrongly- supposed. What was wrong was the definition of a text paragraph in the xml file (including unholy arguments like font-weight-asian and font-weight-complex) which was a left-over from the scan.

To solve the bug I just had to change the paragraph style in the odt.
roger64 is offline   Reply With Quote