Hi Fabrice,
thanks for reporting this. I will be leaving a a break tomorrow and will return on november 3rd.
Although this seems like a quick fix (doing a encoding of the filename), I need time to replicate and test as the filename is also used to download the correct file (so should also be 'decoded' again.
So this has to wait a bit.
fastest 'fix' is to not use the & in the filename and replace it with e.g. a - or _
This is also recommended, see below for the logic of this recommendation:
It is generally considered bad practice to have a filename with an ampersand (&) in it. Here's why:
- Compatibility Issues: Different operating systems and software may interpret special characters like & differently, leading to potential problems when accessing or opening the file.
- URL Encoding: When used in URLs, ampersands often need to be URL-encoded (%26), which can make the filename appear strange or difficult to read.
- Search and Organization: Some search tools and file management systems may not handle filenames with special characters correctly, making it harder to find and organize files.
It's best to avoid using special characters in filenames whenever possible. If you must use a filename with an ampersand, consider using a different character like an underscore (_) or hyphen (-) instead.
