View Single Post
Old 09-05-2013, 08:23 AM   #39
gmw
cacoethes scribendi
gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.gmw ought to be getting tired of karma fortunes by now.
 
gmw's Avatar
 
Posts: 5,818
Karma: 137770742
Join Date: Nov 2010
Location: Australia
Device: Kobo Aura One & H2Ov2, Sony PRS-650
Quote:
Originally Posted by ApK View Post
I was actually surprised that it worked in my example (well, I was surprised it worked in Chrome...IE I've come to expect to be non-compliant). I fully expected to need an &nbsp, or to see Word use some complex style.
I just grabbed a copy of Chrome (v29 apparently), it gets both your example and mine correct on my machine. Is there any chance the editor you were using to create the source used some invisible Unicode space character other than a normal space? ... ETA: Scratch that, looking at the screen capture it's encoding 1252 - not Unicode.

ETA (again). I could simulate what you see by copying a literal non-breaking-space from the character map into an ANSI 1252 encoded text file. If you can get a hex view you may find those "spaces" are 0xA0 characters (if no hex, trying using Ctrl+Right to jump between words and see if it can't find the start of the second testing).

Last edited by gmw; 09-05-2013 at 08:42 AM.
gmw is offline   Reply With Quote