> From: Tim Ruehsen <tim.rueh...@gmx.de>
> Cc: mehw.is...@inventati.org, firstname.lastname@example.org
> Date: Fri, 16 Sep 2016 11:15:31 +0200
> > So if wget needs to create or open such files, it needs to replace the
> > colon with some other character, like '!'.
> That is what I meant with 'Wget has functions to percent escape special
> characters...'. It is not only colons. And it depends on the OS (and/or file
OK, so the problem should not exist, good.
> From https://en.wikipedia.org/wiki/Comparison_of_file_systems:
> "MS-DOS, Microsoft Windows, and OS/2 disallow the characters \ / : ? * " > <
> and NUL in file and directory names across all filesystems. Unices and Linux
> disallow the characters / and NUL in file and directory names across all
This is a better reference, JFYI: