Following up on #2286, there is another issue where pasting content that is not supported by the current console font results in invalid data being transferred to WSL.
Note that this is not a report about broken rendering of unicode/emoji glyphs, etc. This is about the raw data that is being transferred become corrupt on paste.
As an example, copy this emoji to the clipboard 🤷 then follow the steps below:
$ cat | hexdump -C
At the cat prompt, paste the emoji from the clipboard, press Enter, then hit ctrl+D to end the cat read from stdin.
The results are
mqudsi@Blitzkrieg /m/d/G/paypal> cat | hexdump -C
��
00000000 ef bf bd ef bf bd 0a |.......|
00000007
While the 🤷 cannot be rendered by my console font, that should not preclude it from being used (though not correctly represented). However, in this case the "symbol not found" unicode character is put in its place, and that is what comes out in the resulting hex dump.
Following up on #2286, there is another issue where pasting content that is not supported by the current console font results in invalid data being transferred to WSL.
Note that this is not a report about broken rendering of unicode/emoji glyphs, etc. This is about the raw data that is being transferred become corrupt on paste.
As an example, copy this emoji to the clipboard 🤷 then follow the steps below:
At the
cat
prompt, paste the emoji from the clipboard, pressEnter
, then hitctrl+D
to end thecat
read from stdin.The results are
While the 🤷 cannot be rendered by my console font, that should not preclude it from being used (though not correctly represented). However, in this case the "symbol not found" unicode character is put in its place, and that is what comes out in the resulting hex dump.