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
I am using renamer a lot to tidy up the names of downloaded articles, papers etc.
Issues that I encounter a lot are characters such as double quotes "some phrase" which could be defanged into „some phrase“ or : which is invalid on Windows and could be defanged into :, similarly to ? which could be defanged into ?. Additionally \n (LF) occurs in some file names copied based on titles of papers, which is no issue on Linux, but becomes an issue when copying to exfat/FAT32 (etc.).
I wonder how this could be best implemented and whether renamer itself is the right scope or whether it should simply allow to call a post-processing executable (no arguments allowed) to pipe the contents through after they were edited by the user.
What are your thoughts?
The text was updated successfully, but these errors were encountered:
Actually it's less OS-specific than file system specific. I suppose by way of a configuration file and sensible defaults the issue with specific characters being replaced can be tackled.
But thanks for the feedback, in this case I'll look into working on this.
I am using
renamer
a lot to tidy up the names of downloaded articles, papers etc.Issues that I encounter a lot are characters such as double quotes
"some phrase"
which could be defanged into„some phrase“
or:
which is invalid on Windows and could be defanged into:
, similarly to?
which could be defanged into?
. Additionally\n
(LF) occurs in some file names copied based on titles of papers, which is no issue on Linux, but becomes an issue when copying to exfat/FAT32 (etc.).I wonder how this could be best implemented and whether
renamer
itself is the right scope or whether it should simply allow to call a post-processing executable (no arguments allowed) to pipe the contents through after they were edited by the user.What are your thoughts?
The text was updated successfully, but these errors were encountered: