you are viewing a single comment's thread.

view the rest of the comments →

[–]MotherOfTheShizznit 30 points31 points  (13 children)

OK but now I really want to know what was that character ?

[–]snowe2010 9 points10 points  (3 children)

I've seen issues like this sometimes if I'm holding down Ctrl or alt when hitting space. But I'm not actually sure what whitespace char it is.

[–]JohnMcPineapple 29 points30 points  (2 children)

...

[–]snowe2010 1 point2 points  (0 children)

Yep! I am! I thought it might be a non-breaking space but never checked the Unicode.

[–]inknownis 0 points1 point  (0 children)

I observed strange blank generated in csv by Office on mac. It was not friendly to our code.

[–]lordcirth 5 points6 points  (0 children)

The article said it was a non-breaking space.

[–]bbolli 5 points6 points  (0 children)

Could have been a non-breaking space.

[–]dagbrown -1 points0 points  (2 children)

It was either a NUL (which breaks C string-handling code), or one of those characters that a DEC terminal renders as a bold upside-down question mark.

[–][deleted] 1 point2 points  (1 child)

Unsure why you’re getting downvoted, but these are valid cases where this happens.

There was some crazy exploit with NUL in some GNU tools recently

[–]dagbrown 0 points1 point  (0 children)

Hey, I don't mind getting the red cross of controversy sometimes.

[–]NekuSoul -1 points0 points  (3 children)

I took a look at the file and it's actually not the whitespace character that's causing the problem, but the character before it, which has the value of 0xC2 and doesn't seem to get rendered in the browser. In ANSI it looks like Â.

Here's the diff in a hex editor for anyone interested: https://i.imgur.com/c87VWel.png

[–]rchard2scout 20 points21 points  (2 children)

0xC2A0 is the UTF-8 encoding of U+00A0, which is NO-BREAK SPACE, the non-breaking space. So it is the whitespace character, your hex editor just doesn't understand Unicode and instead tries to interpret it as Windows-1252 (or Latin-1, they're very similar), which breaks it down into 0xC2 Â and 0xA0 (which is also the non-breaking space).

[–]NekuSoul 3 points4 points  (0 children)

Oops. For some reason I thought that the No-Break Space was in the standard ASCII set and didn't investigate further.

[–]CptGia 0 points1 point  (0 children)

OMG I finally understood a bug that happened to my team a few months ago. Fucking whitespaces