Windows 7: Problems with unicode characters in file names

[GoogleCodeExporter]

My environment:

  Windows 7 Ultimate (Version 6.1, Build 7601: Service Pack 1, German GUI)
  WinFF 1.3.2
  ffmpeg-git-5d4fd1d-win32-static

Dragging and dropping a filename `ラ.mp4' into the WinFF GUI, then pressing 
the `Convert' button, I see the following in the command line window:

  title Converting Òâ®.mp4
  ...
  C:\Users\Werner\Desktop\Òâ®.mp4: No such file or directory

If I set the `Use CHCP for international characters' checkbox, I get the same 
title but a different slightly different wrong file name:

  C:\Users\Werner\Desktop\├úãÆ┬®.mp4: No such file or directory

This is probably related to issue #5.

Original issue reported on code.google.com by lemzw...@googlemail.com on 9 Jul 2011 at 10:05

• Merged into: #10

[GoogleCodeExporter]

This thread seems the nearest to add (same?) point but under Win XP SP3 (lang.: 
EN - UK):

Inserting filenames of talk mp3s for downsizing - in my case, they do not 
contain 'foreign characters' but may contain the less obvious hyphen 
(unicode?)" — " instead of " - ".
This consistently results in the file mysteriously not being processed despite 
being listed as an operand(?) in the big (files) box. 
Tweak to either accept and process with (Unicode? file name chars) or to reject 
inclusion in operand files(?) box?

Original comment by Priestly...@gmail.com on 6 Dec 2011 at 9:00

[GoogleCodeExporter]

Sorry for not responding earlier, but indeed, this issue is something that we 
have not been able to resolve in a long time. And it was reported before.

Original comment by poipodec...@hotmail.com on 16 Dec 2012 at 4:41

• Changed state: Duplicate

[GoogleCodeExporter]

I'm sending the patch that solved this issue.
The zip file contains exe file.
Also I'm sending source code modified.

Please, let me know if this works.
Thank you

Original comment by fago...@gmail.com on 15 Jan 2014 at 10:50

Attachments:

• unit1.pas
• winff.zip

[GoogleCodeExporter]

I was only now able to test the issue with the latest release (EMMA), and 
unfortunately it's not solved [shall I try your winff.zip archive from #3?].  
In the terminal window opened by WinFF, I now get

  ?.mp4: Invalid argument

so there is still an encoding issue, at least with my computer setup as 
described above.

Since WinFF communicates with ffmpeg via the command line, isn't it possible to 
completely circumvent the problem by renaming the file to ASCII only before 
sending it to ffmpeg, say, and moving back to the original file name afterwards?

BTW, setting WinFF's option `use CHCP' on or off doesn't make any difference.

On the other hand, opening a Windows command line window and after saying `chcp 
65001', I *can* use Winff's ffmpeg.exe binary just fine with Japanese file 
names!

Original comment by lemzw...@googlemail.com on 8 Mar 2014 at 11:23