Solved File Management removing unprintable characters
-
@dafyre said in File Management removing unprintable characters:
@DustinB3403 said in File Management removing unprintable characters:
And since I can't beat it into my users that these characters are bad I have to work around them.
Keep on telling them, and then they'll learn when that one file they need can't be restored because they used some ungodly character in the file name.
Unfortunately it isn't my position to tell them. I report to management, management hands out the beatings.
-
@DustinB3403 said in File Management removing unprintable characters:
@dafyre said in File Management removing unprintable characters:
@DustinB3403 said in File Management removing unprintable characters:
And since I can't beat it into my users that these characters are bad I have to work around them.
Keep on telling them, and then they'll learn when that one file they need can't be restored because they used some ungodly character in the file name.
Unfortunately it isn't my position to tell them. I report to management, management hands out the beatings.
Then tell management to beat harder until they start handing out pink slips when a file gets broken so badly it can't be restored and costs the company money.
-
@DustinB3403 said in File Management removing unprintable characters:
@scottalanmiller said in File Management removing unprintable characters:
@DustinB3403 said in File Management removing unprintable characters:
The file system is a Windows environment with mac users, even from a windows workstation you can put in these unprintable characters in the folder and file names.
So the issue is universal as far as I'm concerned.
The issue has to be on a specific file system. So NTFS, I'm assuming.
Yes, NTFS, but also this affects our backup (it has a stroke on files and folders with unprintable characters and just moves along).
Right, but how we modify the source is the first step.
-
So assuming that we have access to PowerShell here, this should be a start...
$String -replace '[^\p{L}\p{Nd}]', '-' -
That Regex should, in theory, allow you to pass in a file name, and resave it with a hyphen instead of any unprintable character.
You just need to loop through the files.
-
@scottalanmiller said in File Management removing unprintable characters:
That Regex should, in theory, allow you to pass in a file name, and resave it with a hyphen instead of any unprintable character.
You just need to loop through the files.
No way to not have to pass an individual file through this? Hoping to just be able to point this at a directory and it searches file and folder for unprintable characters replacing as it goes.
(I know wish in one hand, crap in the other)
-
@DustinB3403 said in File Management removing unprintable characters:
@scottalanmiller said in File Management removing unprintable characters:
That Regex should, in theory, allow you to pass in a file name, and resave it with a hyphen instead of any unprintable character.
You just need to loop through the files.
No way to not have to pass an individual file through this? Hoping to just be able to point this at a directory and it searches file and folder for unprintable characters replacing as it goes.
(I know wish in one hand, crap in the other)
Something like...
$myFiles=dir -recurse C:\Some\Folder foreach ($file in $myFiles) { $newName=$file -replace '[^\p{L}\p{Nd}]', '-' ren $file $newName } -
@DustinB3403 said in File Management removing unprintable characters:
@scottalanmiller said in File Management removing unprintable characters:
That Regex should, in theory, allow you to pass in a file name, and resave it with a hyphen instead of any unprintable character.
You just need to loop through the files.
No way to not have to pass an individual file through this? Hoping to just be able to point this at a directory and it searches file and folder for unprintable characters replacing as it goes.
(I know wish in one hand, crap in the other)
Well, that's what the loop would be for. One way or another, the files have to be iterated through.
-
@dafyre exactly
-
@dafyre You might want to throw in an if statement there to check that the names are different before you rename.
I'm assuming the ren will rename the file even if the names are the same, but maybe it won't. Some very light testing suggests it may (no errors thrown). -
NTFS is utf-16. All characters are allowed in filenames on NTFS, except reserved characters like
< (less than)
> (greater than)
: (colon)
" (double quote)
/ (forward slash)
\ (backslash)
| (vertical bar or pipe)
? (question mark)
* (asterisk)
and chr(0) to chr(31).If the backup system can't handle all allowed characters in a filename, then that is the problem that needs to be fixed.
There is no such a thing as unprintable characters. Just need the right font that has that character defined.
This is screenshot from Windows showing valid file and folder names:
-
@Pete-S said in File Management removing unprintable characters:
Unrelated to the OP....
Why do those kanji look familiar? Like seriously... -
@DustinB3403 said in File Management removing unprintable characters:
So long story short I have users who use unprintable characters in file and folder paths, such as or the little floating dot.
Can anyone think of some quick way to replace all of these in every folder and sub folder and file with a normal hyphen?
There's some built-in cmdlets to do this pretty easily.
Building on @scottalanmiller's regex, I added the exclusion of punctuation characters, because in my testing, it was replacing the "dot" before the file extension. I did not go looking for a way to just exclude dots. Someone else can do that.
This line will get each item in a directory and subdirectories
-Recurse, and replace any non-"your-language"alphabet character, ignoring regular aphabet/number/punctuation characters.Here's how I'd go about it:
# Remove the -WhatIf when you are ready to make the changes. (Get-ChildItem -Path "C:\test" -Recurse | Rename-Item -NewName {$_.Name -replace '[^\p{L}\p{Nd}\p{P}]','-'} -WhatIf)Using the
-WhatIfswitch will allow the code to be ran while telling you exactly what will change, without actually doing it. Remove the-WhatIfwhen you are ready to make the changes. -
@Obsolesce That is absolutely the perfect answer.
-
@Pete-S said in File Management removing unprintable characters:
If the backup system can't handle all allowed characters in a filename, then that is the problem that needs to be fixed.
While I would generally agree, I have no way to control the file system in my backup location, which complains about the files and just skips them.
So while I agree, use a better back tool that isn't the answer I'm looking for.
@Obsolesce this is great, thank you!
-
A few things to think about:
- Expect some support calls when you rename customer files and they can't open them using "recent files".
- Also expect problems when you rename a file that someone has open. Normally you can't => script fail.
- Also expect problem if someone makes a new file with the original name. Now there will be two files that will have the same name after the renaming process => script fail.
- Also hope that there aren't any application files that will not pass the regex => application fail.
Is the backup something homemade or something very old perhaps?
I suggest spending some time finding out exactly what characters are supported and making sure the regex is exactly that and not anymore restrictive than needed.
Then make sure the renaming script can handle errors mentioned above.
And I suggest some log file or email sent with files that can't be renamed so you know. -
@Pete-S said in File Management removing unprintable characters:
Expect some support calls when you rename customer files and they can't open them using "recent files".
Not my concern in the least
@Pete-S said in File Management removing unprintable characters:
Also expect problems when you rename a file that someone has open. Normally you can't => script fail.
Only targeting files that are marked for "archive" - so not an issue
@Pete-S said in File Management removing unprintable characters:
Also expect problem if someone makes a new file with the original name. Now there will be two files that will have the same name after the renaming process => script fail.
We already punch people in the back of the head for this
@Pete-S said in File Management removing unprintable characters:
Also hope that there aren't any application files that will not pass the regex => application fail.
Nope
@Pete-S said in File Management removing unprintable characters:
Is the backup something homemade or something very old perhaps?
Using B2 CLI to move stuff, so not old at all.
-
This really sounds like an HR problem that you're kinda solving with tech. If it's not against company policy to use those characters in file names/paths - then what you wanting to do is likely the wrong approach... and instead management should be approving you to find a new backup solution that works with those filenames.
-
@Dashrender said in File Management removing unprintable characters:
This really sounds like an HR problem that you're kinda solving with tech. If it's not against company policy to use those characters in file names/paths - then what you wanting to do is likely the wrong approach... and instead management should be approving you to find a new backup solution that works with those filenames.
There is no policy on this, not would there be one.
This is an insane way to think about that.
-
Okay so with a bit more offline assistance from @Obsolesce
This is what works
(Get-ChildItem -Path "some\path" -Recurse | Rename-Item -NewName {$_.Name -replace '•','-'} -verbose)Obviously it's only hitting on that bullet point, and replacing it with a hyphen, but that's better than the operation failing over and over and not ever knowing it.
