Custom paths for exports can result in invalid files in Windows

[t3dotgg]

I have a lot of issues to go through, so in order to make it easier for me to help you, I ask that you please try these things first

• Try with the newest version from GitHub (also it might have been fixed in latest nightly build)
• Read the documentation and FAQ, Known issues, Troubleshooting
• Search for your problem under Issues or Discussions
• If you have a problem only with a particular file (or file type), use this form instead
• Windows 7, 8 and 8.1 are no longer supported. This is not a question about Windows 8.1 or older.

Operating System

Windows 10

Steps to reproduce

Hey y'all! Had a few issues where certain characters sneak into path names and break things badly in Windows. Biggest causes are spaces at end of file names and "..."

Expected behavior

File paths should be valid

Actual behavior

File paths are invalid and break windows

Share log

No response

[mifi]

Hi! This is with "No sanitize" right? (in the output file name template export settings):

I think we could indeed still add some sanitazion even for the "no sanitize" mode. Do you have any concrete examples of file names that failed? I see that your screenshot has a file named 09 - End_of_Prime_reacts_to_is - but I cannot see any .. or trailing space there. And I cannot find any documentation saying the file names on windows cannot contain .. or trailing space.

what does the output look like in the "preview" button dialog?

[t3dotgg]

This is happening with sanitize on sadly

[mifi]

I have now changed logic when sanitize is on:

• disallow both forward and backward slashes on windows
• disallow file name ending with a space or a dot