Quote:
Originally Posted by Gregg Bell
I know they're the same thing but Sigil never changed the before. Is this normal? So then if there is a lone in the book somewhere I really should look for & #160; right?
|
In 2019, I reported the same bug in the "Sigil 0.9.15" thread:
https://www.mobileread.com/forums/sh...64#post3865864
Nobody could find any rhyme or reason it happened either.
... Definitely a headscratcher though... (it hasn't happened to me since).
Diap recommended the same thing here: To readd the or   as needed.
Quote:
Originally Posted by Gregg Bell
(I left that space in & #160; intentionally otherwise MR turned it into *)
|
The forums auto-convert nbsp and #160 into space.
If you want to force it to display, you can shove a
[ noparse][/noparse] around the ampersand. (Remove the space before " noparse".)
So you type this:
Code:
[ noparse]&[/noparse]nbsp;
[ noparse]&[/noparse]#160;
and the forums will display like this: