&()nbsp , &()#160 , inconsistencies??
I am quite familiar with the interchangeability of these two codes* for a blank space - but do they have to go this far??
*obviously without the brackets, but they don't display otherwise do they??!!
I was editing a book, removing (in particular) double spaces created in the epub conversion.
Doing fine, replacing &()160 with spacebar spaces.
Had to rush away from PC, so saved file and closed Sigil (only - not PC).
False alarm, so returned 5 mins later, opened same file with same version of Sigil to continue replacement - and 'Search (find)' wouldn't find &()160.............because on reopening the spaces had all become &()nbsp; 's !!!!!
Whatever caused that behaviour? Small, easily solved problem (once noticed!) but why did it do it in the first place??
Thanks
|