search

amikey / winff

Automatically exported from code.google.com/p/winff
0 stars 0 forks source link

Windows account name with international characters = error #51

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Creating a Windows account name in Cyrillic
2. Install and run WinFF 1.0.4
3. Take error message «unable to create file ""»

What is the expected output? What do you see instead?
Unable to create file “”.
Press Ok to to ignore and risk data corruption.
Press Cancel to kill the program.

What version of the product are you using? On what operating system?
WinFF 0.4 - 1 - 1.0.4
Windows 7 RC - 7600

Please provide any additional information below.
this non-latin guy take similar error message: http://
www.onmy.org/2009/06/24/winff-error/

Original issue reported on code.google.com by axle...@gmail.com on 23 Jul 2009 at 12:32

GoogleCodeExporter commented 9 years ago 
This bug report should have been attached to bug 10, because it is probably 
related
to it.

Coming from the forum: http://www.biggmatt.com/forums/index.php?topic=466.0
I don't understand the forum comment:

"Maybe it makes sense to store program settings in the catalog winff? At least 
optional?"

Original comment by poipodec...@hotmail.com on 23 Jul 2009 at 1:39

GoogleCodeExporter commented 9 years ago 
> I don't understand the forum comment.

Bad English, sorry. I meant move settings-folder from 
%userprofile%\appdata\roaming
\winff to c:\program files\winff (not multiuser version).

Original comment by axle...@gmail.com on 23 Jul 2009 at 1:54

GoogleCodeExporter commented 9 years ago 
Sorry, but if I could have the complete source code, I could look where the 
problem
occurs (exact execution line). I think it's at some place where the path 
location is
get from Windows (in Ansi or Unicode/WideChar) and then next routine uses it as 
OEM
or in a bad conversion (to/from Ansi/Unicode).

yours, Daniel
from Brazil
danielcalegar@yahoo.com

Original comment by danielgu...@gmail.com on 25 Jul 2009 at 8:25

GoogleCodeExporter commented 9 years ago

Original comment by bgg...@gmail.com on 22 Oct 2009 at 9:00

GoogleCodeExporter commented 9 years ago 
Issue 59 has been merged into this issue.

Original comment by bgg...@gmail.com on 22 Oct 2009 at 9:02

GoogleCodeExporter commented 9 years ago

Original comment by bgg...@gmail.com on 2 Nov 2009 at 1:57

GoogleCodeExporter commented 9 years ago 
can somebody zip a user folder with these characters in it and send to me ?

istoff -> gmail -> com

Original comment by istoff@gmail.com on 4 Nov 2009 at 2:10

GoogleCodeExporter commented 9 years ago 
Issue 67 has been merged into this issue.

Original comment by bgg...@gmail.com on 22 Mar 2010 at 1:43

GoogleCodeExporter commented 9 years ago 
Issue 96 has been merged into this issue.

Original comment by bgg...@gmail.com on 3 Oct 2010 at 3:53

GoogleCodeExporter commented 9 years ago 
Issue 106 has been merged into this issue.

Original comment by poipodec...@hotmail.com on 5 Jan 2011 at 7:40

GoogleCodeExporter commented 9 years ago 
Any path names & filenames on Windows using these characters fails in bat files 
and .vbs files I've tried.

It's a problem that WinFF is inheriting from the file system.

Not sure if we can ever fix this. 

Can we close these issues on Windows?

Ian

Original comment by istoff@gmail.com on 5 Sep 2011 at 5:23

GoogleCodeExporter commented 9 years ago 
Wouldn't it be possible to fix this issue the moment that we start using the 
libav library instead of the ffmpeg binary? Than you don't need to pass around 
arguments via files.

Original comment by poipodec...@hotmail.com on 5 Sep 2011 at 9:43

GoogleCodeExporter commented 9 years ago 
probably.

that's still a ways off though.

Original comment by istoff@gmail.com on 6 Sep 2011 at 4:33

GoogleCodeExporter commented 9 years ago 
Issue 161 has been merged into this issue.

Original comment by poipodec...@hotmail.com on 5 Apr 2012 at 6:07

GoogleCodeExporter commented 9 years ago 
Ian/Matt: does this help?

http://stackoverflow.com/questions/9849486/is-it-possible-to-use-extened-ascii-c
haracters-in-bat-file

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

GoogleCodeExporter commented 9 years ago 
Would the same trick as in commit 796 not also work on this problem?

Original comment by poipodec...@hotmail.com on 1 Feb 2014 at 1:20

GoogleCodeExporter commented 9 years ago 
How about changing all calls of
x := tprocess.Create(nil)
to
x := tprocessUTF8.Create(nil)
?

Original comment by poipodec...@hotmail.com on 11 Jun 2014 at 7:48