[roger64]

@Toxaris

I make a bug report because this change for the worst is clearly a new behaviour of Sigil 0.7.2 . I do hope that it is something that has just been overlooked and that hopefully it is not intended.

This is the case for "stillborn" &nbsp, I mean &nbsp that have not yet been saved but have been always clearly and easily recognized by older Sigils (and displayed as   ). Forgive me for giving no more technical details of which I am unsure but you can check the test epub with old Sigil... The displayed code is true  

I'd like to get a reply from one Sigil dev on this, because it could well be that other entities are concerned.

The alternative for me would be, once I produce an EPUB file, to save it first with an old Sigil, and to use it later with the new one. Hardly a progress... you guess.

EDIT

I can duplicate this exact same behaviour with Calibre produced EPUB of the same odt file. So you should also add this software to the ones with a faulty export function which is not creating correct   ... I'll attach the files. If you need more examples, just tell me.