Non ASCII accented characters in exiftool input parameter

[disconnect]

Hi the problem is under window 10 pro, both in plain cmd, or powershell:

exiftool -ee -p gpx.fmt ".\20200602_204713 Pilisteto-Két bükkfanyereg.MP4" > gepeiksz.gpx
Error: File not found - ./20200602_204713 Pilisteto-KÚt b³kkfanyereg.MP4

The file name is completed by shell itself by pressin TAB, yet the accented chars gone wrong.
Is there a solution for this?

[StarGeek]

Have you tried FAQ #18?

Windows command line has always been very unfriendly to characters that aren't simple ASCII characters and I've usually had huge problems with this.

That said, as part of the craziness, I copied you example name and renamed a file to the same thing and the newer Windows Terminal all had no problems finding and displaying data from the file, though the it auto-completed the name to be 20200602_204713 Pilisteto-Kt bkkfanyereg.MP4.

[disconnect]

There is no problem displaying non-ascii characters in console, but as you can see from the copied text, the input is correct, but the characters in error message are wrong.
Tried charset, and setting cp, nothing changed.
It seems that exiftool is what can't accept non ascii characters

[Phil Harvey]

What character set are you using the console?  And what setting did you use for the exiftool -charset filename option?

- Phil

[disconnect]

Here is a copy paste from console

Code Select Expand

g:\goprp\20200527>chcp 65001
Active code page: 65001

g:\goprp\20200527>powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS G:\goprp\20200527> exiftool -charset filename=utf8 -ee -p c:\Progz\rclone\gpx.fmt ".\20200527_170633 Őzike.MP4" > gepeiksz.gpx
Error: File not found - ./20200527_170633 Ozike.MP4
PS G:\goprp\20200527>

[Phil Harvey]

Interesting.  That looks like it should work.  I don't have experience with PowerShell, but that should work in cmd.exe.

- Phil