53714abfa3
The problem demonstrated in #6065 is that a string has incorrectly been encoded with US-ASCII even though it contains invalid US-ASCII byte sequences (any byte with the most significant bit on is invalid in the US-ASCII encoding). The thing about doing newline normalization is that it is not actually sensitive to the presence of US-ASCII byte sequenzes. Additionally, it is very unlikely that a user will ever be using an encoding where \r\n is not encoded the same as it would be in ASCII. This patch first tries the existing method of normalizing the newlines in the provided script file, if that fails for any reason it force encodes the string to ASCII-8BIT (which allows the most significant bit to be on in any individual byte) and then performs the substitution in that byte space. |
||
|---|---|---|
| .. | ||
| ansible | ||
| cfengine | ||
| chef | ||
| docker | ||
| file | ||
| puppet | ||
| salt | ||
| shell | ||