You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Files uploaded with the material editor do not preserve their filenames when downloaded, if they include (non-ASCII) unicode characters.
To Reproduce
Steps to reproduce the behavior:
Go to 'Material Editor'
Upload file with filename (for example) 'TEST日本語123.txt'
Go to the event page, right-click and download the file above.
The downloaded file has a filename 'TEST123.txt', which is different from the original.
Expected behavior
In the example above, the downloaded filename should be 'TEST日本語123.txt' instead of 'TEST123.txt'.
Screenshots
Here is a screenshot of how the file looks in the agenda page (it is correct here):
This shows that, at least in this intermediate step, the filename seems to be properly stored.
However, the actual URL to the file (and therefore how the web browser saves the file) does not have the correct filename.
Here is a screenshot of the web browser pointing to the file:
We currently strip all non-ascii characters from filenames because back when writing this code a few years ago, browser support for unicode filenames wasn't as good as it is now, so it was the right thing to do.
However, you are right that we should start sending the original filename when downloading a file, and I could have sworn that I created an issue for this a few months ago when implementing this for another case where users can upload files... anyway, now that you created one we have one. :)
Describe the bug
Files uploaded with the material editor do not preserve their filenames when downloaded, if they include (non-ASCII) unicode characters.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
In the example above, the downloaded filename should be 'TEST日本語123.txt' instead of 'TEST123.txt'.
Screenshots
Here is a screenshot of how the file looks in the agenda page (it is correct here):
This shows that, at least in this intermediate step, the filename seems to be properly stored.
However, the actual URL to the file (and therefore how the web browser saves the file) does not have the correct filename.
Here is a screenshot of the web browser pointing to the file:
Additional context
The text was updated successfully, but these errors were encountered: