Skip to content

Conversation

@Robby-Swartenbroekx
Copy link

if there are some special characters in filepaths, select-string failed. With adding quotes around the pathname, this is solved.

@prejay
Copy link
Contributor

prejay commented Dec 21, 2021

I've added your update through as 0.2.2 but I was still seeing a problem wth characters not reading correctly eg © ℗®™
Have also updated robocopy to a unicode logging (0.2.4) and the csv import to UTF7 encoding (0.2.4.1) which appears to have solved the problem wth the characters I was seeing re the display, but I'm still seeing select-sring fail.
Not sure whether you've got any others you can test with to confirm?

Log:
c:\Program Files\Progress\DataDirect\Connect64_for_ODBC_71\Uninstall Progress DataDirect Connect64 © and Connect64 XE for ODBC 7.1\uninstaller.jar

Script:
select-string : Cannot find path 'C:\Program Files\Progress\DataDirect\Connect64_for_ODBC_71\Uninstall Progress DataDirect
Connect64 © and Connect64 XE for ODBC 7.1\uninstaller.jar' because it does not exist.
At line:128 char:11

  •       select-string "JndiLookup.class" "$($_.FilePath)"
    

@Robby-Swartenbroekx
Copy link
Author

Hmm, strange, I have about the same (also Progress), but with me this does work:

select-string "JndiLookup.class" "D:\SORTED\P\Progress\Progress® SavvionT Process Modeler 8.0.0.1\PROGRESS_SAVVION_PROCESSMODELER_8.0.0.1_ALL\Installer\setup.jar"

This doesn't give any errors. Even making it longer and add extra special characters, it doesn't stop select-string from processing it. The only thing I find strange is that ™ is viewed as T when I copy this character to a powershell window. But that is only a viewing thing, because if I change that character by a regular T, it says it doesn't find the path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants