@DiapDealer
You explained us not long ago where the trouble was coming from (underline is mine):
Quote:
|
I (and I suspect Kevin, as well) would love to be able to support the use of the unicode character for the nobreak space in Sigil. The current parser (Google's Gumbo) could handle them just fine. Unfortunately, the unicode character cannot survive Qt's QTextEdit environment, which Sigil uses for Code View/Book View. They get changed to "normal" spaces. Hence the entity to keep that from happening.
|
Then you had spoken about "
the unicode character". That's why I had hoped that using one
hexadecimal character could provide a workaround for writing the no-break space with a discrete display. It could also have given the user a possibility to share the same character for both the Calibre Editor and Sigil.
Does the -now- notorious QTextEdit bug has really so long arms and extend to all kinds of representation of the nobreak space?