Thread: regex - issue with spaces?
View Single Post
Old 12-29-2013, 05:15 PM   #33
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,823
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by theducks View Post
It only applies to (friendly) Named entities. You can still use their entity-numbered ,ISO-8859-1 versions Again & #160 is a NBSP
just like & #62 is a >

It is just a PITA to have to keep a chart handy
Perhaps the editor could have a set of preferences that would allow the user to assign keyboard shortcuts to commonly used 'entities' like non-breaking-space, em-dash etc. I've done it with AHK, but I always prefer using built-in features rather than 3rd party gadgets.

@mrmikel - sorry, I misinterpreted your comment as meaning 'non breaking spaces' should be removed irrespective of their representation - hence 'banished'.

I don't care if its represented by  , #160, an A0, or a cube of sugar - as long as I can 'see' it when I'm reading the book.

BR
Last edited by BetterRed; 12-29-2013 at 06:01 PM. Reason: move Off Topic paragraphs
BetterRed is online now   Reply With Quote