#2 Unicode Support?

[Anonymous]

This plugin doesn't seem to support files with unicode naming? I would like to see it implemented if possible, although another alternative is simply to rename the files myself, it might be more practical to add unicode support to the plugin so that it can be used by people from different countries.

[Peter Belkner]

I'm not certain whether I'm understanding the request. Are you able to process your files using command line SoX (http://sourceforge.net/projects/sox/files/sox-win/14.3.1/) and FFmpeg (http://ffmpeg.arrozcru.org/autobuilds/)?

[Nobody/Anonymous]

with winamp's default input plugins, im able to play my songs which has japanese characters in the file name, for example. when i switched over to your plugin, i can't play them anymore

[Peter Belkner]

Ask the question in the Winamp forum:

http://forums.winamp.com/showthread.php?p=2679991#post2679991

Hopefully somebody can advice ...

[Peter Belkner]

Just to make it clear: I've asked the question.

[Peter Belkner]

Have developed a little test program and posted it in the Winamp forum:

http://forums.winamp.com/showthread.php?p=2680050#post2680050

Have also uploaded a binary version to the Winamp forum:

http://forums.winamp.com/showthread.php?p=2680079#post2680079

Could you please run this test and tell me wether the program can open your files?

[Peter Belkner]

ZIP containing "test.c", "test.exe", and "Makefile".

[Peter Belkner]

The "test.zip" is also attached to this tracker, see below.

[Nobody/Anonymous]

I got "error opening file" in it.

[Peter Belkner]

ZIP containing "test.c", "test.exe", and "Makefile".

[Peter Belkner]

Could you please try the "test.exe" from the "test-1.zip" (see below)?

The difference is that the new version uses the wcstombs() method (cf. e.g. http://www.mkssoftware.com/docs/man3/wcstombs.3.asp)

Thanks in advance!

[Nobody/Anonymous]

same here, still getting "error opening file" in it.

i don't know if this helps, but the first test.exe, it shows: 02 - xxx.flac , where xxx will show some gibberish. While the 2nd test.exe, it shows: 02 multibyte string, followed by just 02 in the later lines.

Note that the folders all have normal latin characters in them, just the name of the file is in japanese.

[Peter Belkner]

Maybe you could upload a small sample file, only a few seconds to keep it as small as possible?

[Peter Belkner]

ZIP containing "test.c", "test.exe", and "Makefile".

[Peter Belkner]

Could you please try the "test.exe" from the "test-2.zip" (see below)?

The new version tries to convert the file name from Windows wide characters to UTF-8.

Thanks in advance!

[Peter Belkner]

All these tests will not work, maybe except the first one. The other tests are based on the assumption that fopen() accepts UTF-8 strings, but unfortunately that seems not to bes the case on Windows.

The only way out may be the first approach which is based on the idea to convert Windows wide character file names first into a DOS 8.3 file names. Meanwhile I've learned that unfortunately not all file systems support DOS 8.3 names.

Could you please test whether your file system supports DOS 8.3? If you e.g. CD to "C:\WINDOWS" and run "dir /X" you should see some of them:

C:\WINDOWS>dir /X
Datenträger in Laufwerk C: ist ACER
Volumeseriennummer: 480B-8811

Verzeichnis von C:\WINDOWS

01.03.2004 14:27

.
01.03.2004 14:27 ..
01.03.2004 14:13 system32
01.03.2004 14:13 system
01.03.2004 14:27 repair
01.03.2004 14:27 HELP Help
01.03.2004 14:27 CONFIG Config
01.03.2004 14:27 msagent
01.03.2004 14:27 CURSORS Cursors
01.03.2004 14:27 MEDIA Media
01.03.2004 14:27 java
01.03.2004 14:35 WEB Web
01.03.2004 14:27 addins
01.03.2004 14:27 CONNEC~1 Connection Wizard
01.03.2004 14:27 DRIVER~1 Driver Cache

...

28.12.2007 18:28

WBEM
28.12.2007 18:30 79.843 KB9426~1.LOG KB942615-IE7.log
28.12.2007 18:28 IE7UPD~1 ie7updates
13.03.2009 06:39 6.486 KB9384~1.LOG KB938464-v2.log
28.12.2007 18:33 10.997 KB9381~1.LOG KB938127-IE7.log
26.04.2009 11:23 97.651 KB9630~1.LOG KB963027-IE7.log
28.12.2007 19:18 680 hpinfo.lnk
23.05.2002 03:00 20.480 INRES.DLL
22.11.2008 08:42 90 setuplog
268 Datei(en) 21.717.580 Bytes
53 Verzeichnis(se), 17.291.264.000 Bytes frei

Then CD to the folder where your files are located and run "dir /X" again. Do you see the DOS 8.3 names? If not, copy one of the files into a file system supporting DOS 8.3 names. Does the "test.exe" from the first "test.zip" open it? If this works I would like to support at least this (limited) support depending on the file system.

[Peter Belkner]

Contains "in_ffsox.dll" v0.3.1a1

[Peter Belkner]

Could you please test the version v0.3.1a1 (see attachment below)? It is based on the following assumptions:

* The file system supports DOS 8.3 short names. 
* The DOS 8.3 short names are composed only from an 8 bit range.

Based on these assumptions the unicode file name is converted in a DOS 8.3 name and the file is tried to open using the DOS 8.3 name.

[Nobody/Anonymous]

still no good, i'm using ffsox with xmplay and any file with foreign character won't be played by ffsox...

[Peter Belkner]

As stands it's a limitatation of FFmpeg, cf.

http://ffmpeg.arrozcru.org/forum/viewtopic.php?f=9&t=607

It's out of scope from this project to fix FFmpeg.