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
Right now much of the processing of files goes through getAbsolutePath().toUri().toString() which breaks at the toUri() step when there's a space in the file.
Specifically you get a %20 in the filename instead of a space.
The text was updated successfully, but these errors were encountered:
To avoid introducing URL encoding into a local filesystem path, can we first check that the path is a valid URI? If so, we can convert it via the current method toUri().toString(), if not, we treat it as a local path and only use .toString(). A single method could perform the check and output the correct string based on the input path.
Right now much of the processing of files goes through getAbsolutePath().toUri().toString() which breaks at the toUri() step when there's a space in the file.
Specifically you get a %20 in the filename instead of a space.
The text was updated successfully, but these errors were encountered: