[EMAIL PROTECTED] (Steven M. Schweda) writes: > It does seem a bit odd that no one has noticed this fundamental > problem until now, but then I missed it, too.
Long ago I intentionally made Wget use binary mode by default and not muck with line endings because I believed exact data transfer was important to get right first. Unfortunately EOL conversions break automatic downloads resumption (REST in FTP), manual resumption (wget -c), break timestamping, and probably would break checksums if we added them. Most Wget's users seem to want byte-by-byte copies, because I don't remember a single bug report about the lack of ASCII conversions. The one thing that is surely wrong about my approach is the ';type=a' option, which should either be removed or come with a big fat warning that it *doesn't* implement the required conversion to native EOL convention and that it's provided for the sake of people who need text transfers and are willing to invoke dos2unix/unix2dos (or their OS equivalent) themselves.
