Michael Jennings <[EMAIL PROTECTED]> writes: > However, I have a comment: There is simple logic that would solve > this problem. WGet, when it reads a line in the configuration file, > probably now strips off trailing spaces (hex 20, decimal 32). I > suggest that it strip off both trailing spaces and control > characters (characters with hex values of 1F or less, decimal values > of 31 or less). This is a simple change that would work in all > cases.
The problem here is that I don't want Wget to randomly strip off characters from its input. Although the control characters are in most cases a sign of corruption, I don't want Wget to be the judge of that. Wget currently has clearly defined parsing process: strip whitespaces at the beginning and end of line, and around the `=' token. Stripping all the control characters would IMHO be a very random thing to do. If I implemented the support for ^Z, I'd only strip it if it occurred at the end of file, and that's somewhat harder.
