[roger64]

Hi

To illustrate what I consider to be a calibre Editor bug, I used a book that I published on MR last year. But I found the same defect for the same kind of files on another book.

The EPUB file included below has been converted by writer2xhtml from the odt file (also included). I have been using writer2xhtml for the last three years. Please pay attention that the EPUB file below has never been saved and is coming straight from the converter. It's a kind of virgin on this regard. There is still some homework to do to finish this EPUB.

a) I need the following three-step process to get a clean EPUB with the calibre editor:

1. - opening the EPUB with Sigil 0.6.2 and saving it (just to rescue 611 nbsp from imminent slaughter). It includes also 1971 nnbsp (such is French language)
2. - opening the EPUB with Sigil 0.7.4 and doing some homework
3. - opening with calibre Editor and finishing the homework
Doing it this way, I can get out of any problem but of course it's a tedious and unintuitive process...

b) Why not open it directly with the calibre Editor? I did try it and it triggers a big problem with the display of each of the two embedded otf fonts:
On top of some small defects, the Editor reports the two following mistakes that I was unable to repair:
- le fichier n'est pas référencé (non referenced file)
- la ressource liée n'existe pas (linked resource does not exist).
I maybe wrong but I think these two above mistakes are self-inflicted by the calibre Editor: when I open directly the EPUB with the calibre Editor, it writes a book.opf file (Sigil does the same but names it content.opf). Opening this book.opf file, I can see in the manifest that the items representing the otf fonts are wrongly written.

I can read: <item href="styles/LinLibertine etc. instead of <item href="Fonts/LinLibertine etc.

I let you compare by yourself the differences obtained when
- first saving with old Sigil version (6.2)
- first saving with calibre Editor.