Converting space to non breaking space
It seems that recently Teams starting converting space characters to non breaking space characters. The text with non breaking spaces doesn't work the same, e.g. a search query that not fails.
The engineering team has created a fix for this that is currently making its way thru our internal testing. You should see the fix soon. Thanks.
PLEASE PLEASE dont delete the whitespace!!!.. Have mercy on us!!.. this is driving me crazy!
Wow, still broken... Good job, MS.
it's 2020 how are you getting on?
Matt Baker commented
Wasted quite a while before pasting into a hex editor and noticing spaces are 0xA0 instead of 0x20!
This is still broken
Bill Bradbury commented
Same problem for me, copied working SQL into Teams for a colleague to run.
He copied it from Teams and ran it, but it gave an error.
So I copied it back from Teams and it no longer ran for me either.
It looked the same as the original.
I did a Hexdump and could see anywhere with two or more spaces, Teams had changed the extra spaces to hex a0 (the "non breaking space" Trevor mentioned)
So currently Teams cannot be used to share code snippets in Chat.
Is there a setting that can be changed to stop Teams replacing spaces with non breaking spaces?
This has caused a number of issues following our recent enterprise migration from Slack to Teams, and the explanation is not obvious for non-expert users. Another vote for this being very annoying...
Steve Rolfechild commented
This breaks ``` for code sharing - how annoying
we get this problem in copy/paste CODE with hard space. Trouble trouble trouble
in code quoted text. (```)
David Rawlins commented
Google led me here.
This is quite a problem as we often share code snippets through Teams chat and you have to resort to Notepad++ to convert back to true space. Very annoying and utterly unnecessary :(
This is a deal breaker for my development team, we're defying management and going back to Slack.
This is the main reason programmers use Slack, certainly the main reason for me.
Let us be thankful Teams doesn't swap out hyphen for mdash.
JSON has been the most painful so far, because it converts valid JSON into invalid JSON. See the attached files. valid.txt was pasted into Teams using ```. invalid.txt is what was copied.
JSON has been the most painful so far, because it converts valid JSON into invalid JSON. See the attached files. valid.json was pasted into Teams using ```. invalid.json is what was copied.
Note that it only seems to happen to leading spaces
I'm seeing this issue when using both ``` and code snippets. This makes copying/pasting code very painful.
Philippe Laplanche commented
this replacement is enabled when using ``` shortcut to start inserting code but disabled when using the "insert code snippet"
Philippe Laplanche commented
this is a terrible idea - This becomes a nightmare to exchange source code / shell commands with MS Teams