I'll take a look in a bit; Safari was the one main system I hadn't tested it on.
I opined elsewhere that part of the problem with SMF's fixes to this problem is that they didn't have a battery of tests to work on, meaning that they were fumbling around in the dark trying to find directions. In the same discussion, I noted that the list of tests to be carried out is:Quote In fact I realise I missed single and double quotes off the list but " is not valid in most systems' filenames anyway. (And in the code I wrote, it would be safely rawurlencode'd anyway)
I opined elsewhere that part of the problem with SMF's fixes to this problem is that they didn't have a battery of tests to work on, meaning that they were fumbling around in the dark trying to find directions. In the same discussion, I noted that the list of tests to be carried out is:
* A filename with no special characters or symbols other than file delimiter (file.txt)
* A filename with 7-bit symbols characters, but no spaces and no + (file_test.txt, file-test.txt)
* A filename with 7 bit characters, and a space (file test.txt)
* A filename with 7 bit characters, and a + (file+test.txt)
* A filename with 7 bit characters, and a space and a + (file test+results.txt)
* A filename with high bit characters (any ISO encoding, on ISO encoded forum) (file™.txt)
* A filename with high bit characters and a space (ISO encoding) (file name™.txt)
* A filename with high bit characters and + (ISO) (file+test™.txt)
* A filename with high bit characters and a space and + (ISO) (file test+results™.txt)
All of the high bit character tests will then need to be repeated on a UTF-8 forum with UTF-8 encoded filenames, and if any of the 7 bit tests fail, there is no point with the high bit tests until the 7 bit tests pass.



