Character encoding in Windows #272
Description
When I'm reading the License file that has control characters, for example the license file of whatwg-url version 5.0.0, characters appear like ÔÇô. Those probably represent non-breaking whitespaces and or other control characters (it's between a 2015 and 2016 see here on npm).
Can the tooling ensure that the encoding is selected correctly that it can also read those characters?
On Linux it works fine it seems, thats why i suspect its an encoding issue.