[BugReport] Unicode Filename..

[akiza]

OS: XP SP2
Language:Trandition Chinese

VLC 0.84a

============

VLC can open English and Chinese FILENAME

But can't open filename contain JAPANESS-CHARACTER....@@

I also try the 0.85 Beta 3

0.85B3 seems don't fix the problem

[DJ]

It is my understanding that 0.8.4 did have problems in this regard. However it was supposed to be fixed in 0.8.5 Considering 2 things:

1. It would be best to download 0.8.5 Test 3 as this is what is current at the moment.

http://downloads.videolan.org/pub/video ... 8.5-test3/

2. VLC uses the system to display fonts in your language. If you don't have these fonts on your system or SP2 was added after your initial setup for languages in your system you may need to go back to the system setup for languages within Windows before VLC will work properly.

[Guest]

OS: XP SP2

VLC 0.84a

============

I have a similar problem. VLC is bypassing song from a m3u -list, when teh filename is including special Signs. like ? or Umlaute ä; ö, ü or ß.

[Guest]

It is my understanding that 0.8.4 did have problems in this regard. However it was supposed to be fixed in 0.8.5 Considering 2 things:

1. It would be best to download 0.8.5 Test 3 as this is what is current at the moment.

http://downloads.videolan.org/pub/video ... 8.5-test3/

2. VLC uses the system to display fonts in your language. If you don't have these fonts on your system or SP2 was added after your initial setup for languages in your system you may need to go back to the system setup for languages within Windows before VLC will work properly.

1. I have tried the 0.85 Test 3, It got the same problem...

2. But my windows can "display" those JAPAN character.
Windos built-in file manager and MPC (Media Player Classic ) can open those file and display/show filename correctly....

So I think that's not OS/SYSTEM's problem....

[DJ]

I do suppose some how it is broke again as even the developers say that this is an area of problems. However I went round and round with a gentlemen in France. MPC would work for him and VLC would not. It ended up being a Windows problem after the install of SP2. When he went back and reinstalled all the languages he wanted in Windows everything worked in VLC.

Unfortunately, unlike the man in France I can not prove this for you. You are going to have to prove it for yourself.

[akiza]

Thanks..^_^

BUT....

My system/OS came with SP2 ( not upgrade from sp1 or older version..).

It's no reason to "downgrade" to SP1 then "upgrade" to SP2,right?

So I think the problem is VLC's in UNICODE moduler not in the OS( SP2)

=========================

And I haven't insyalled any EXTRA language. The system only exist the native unicode come with XP SP2

So I don't understand what extra language we need in unicode system ?

(what's unicode for ?..^_^ . Let people don't need to installed extra language, isn't it ? )

=========================

my english is very poor...@@

[DJ]

I don't think this is a language problem for understanding but instead a misconception!

1. You are not downgrading and then upgrading. You are simple being sure that all of the necessary files to display the desired language exist on your machine. The problem did show up as a SP2 related issue.

2. As far as Unicode goes this is a term tossed around allot, but I don't believe it has anything to do with languages.

3. Just because Internet explorer displays the correct language or another program displays the correct language does not mean that there is not a problem with the system. VLC is very system dependent where many other programs provide everything needed to display languages VLC relies on the system.

4. If you have never set up Windows for the languages of choice and have relied on the original setup this is very possibly the problem.

[HyperHacker]

Hm, I get this too with 0.8.5. I tried a video that plays fine normally, and added Japanese characters to the name. VLC wouldn't open it anymore, and actually kept reporting the error over and over (replacing the character with a question mark) until I closed it, probably because it's set to repeat the playlist. Tried with both Hiragana and Katakana characters.

[DJ]

Actually I think is has everything to do with font and character recognition.

http://alis.isoc.org/codage/iso8859/jeuxiso.en.htm
ISO Standard for various characters sets.

[vlc User]

I can also confirm this bug. vlc 0.8.5 will not open files with unicode character filenames on WinXP (SP2).

[DJ]

How about I put it this way! VLC is a single source code that is compiled on the box and operating system it is intended for, using the resources of that operating system. As such it is reliant on that operating system for support such as languages. It can only use the languages that are installed on that system. It also relies on the operating system for any open file commands and the boxes you see when opening a file are produced by the operating system not VLC. Languages according to Microsoft are divided into groups like Western European and there are ISO character sets that govern this.

http://alis.isoc.org/codage/iso8859/jeuxiso.en.htm
ISO Standard for various characters sets

If the character set for Windows or for VLC is incorrect you will have problems with file names, menus and most probably subtitles.

By default VLC chooses the language installed on your system. If you have never set up your system and have relied on Windows to do it for you or you have more than one language installed on your system you may need to reset Windows and set VLC to the language of your choice in Preferences.

[Guest]

It can only use the languages that are installed on that system. It also relies on the operating system for any open file commands and the boxes you see when opening a file are produced by the operating system not VLC. Languages according to Microsoft are divided into groups like Western European and there are ISO character sets that govern this.

While you are partially right, it's no useful solution. As it is now, vlc is compiled non-unicode on win32 platforms. This means that all characters need to be translated to the systems codepage. And to switch your systems codepage on systems up to WinXP atleast, requires a reboot, which is an unnecessary step for viewing filenames of different character sets (like korean, russian, japanese). It DOES NOT have to be this way. They could simply[*] compile a unicode version and all would be swell on the win32 platforms.

[*] not quite true, since vlc probably insists on keeping support for the godforsaken Win9x platforms. (If you ask me, they can go the way of the MacOS 9 port.) But there is a solution for running unicode programs on win9x platforms: The Microsoft Layer for Unicode on Windows 95/98/Me Systems (see http://libunicows.sourceforge.net/ for further information.)

So, while changing the systems codepage, or changing the filename are workarounds, they are not optimal solutions.

Start compiling vlc with unicode support.

This is still a valid bug/feature request.

[md]

These problems have been fixed recently - but only on Unicode-capable Windows versions
(NT,2000,XP,Vista)

Please try:

http://download.videolan.org/pub/testin ... -win32.exe

[Paul Kuhn]

These problems have been fixed recently - but only on Unicode-capable Windows versions
(NT,2000,XP,Vista)

Please try:

http://download.videolan.org/pub/testin ... -win32.exe

under WinXP with SP2 always the ...

[md]

Could you please post the exact filename, directory name, method how you're trying to open the file and debug messages from vlc?

[Paul Kuhn]

Could you please post the exact filename, directory name, method how you're trying to open the file and debug messages from vlc?

I tried to open a VDR recording via XXV Web Service. This service generate a m3u-playlist.
This is its content:
\\vdrserver\video\Loeschtest\Dragon_Hunters\Dragon_Hunters_-_Die_Drachenjäger\2006-11-15.17.00.01.01.rec\001.vdr

The output of the VLC is:
main error: cannot resolve \\vdrserver\video\Loeschtest\Dragon_Hunters\Dragon_Hunters_-_Die_Drachenj?ger\2006-11-15.17.00.01.01.rec\001.vdr port 554 : Host or service not found
access_realrtsp error: cannot connect to \\vdrserver\video\Loeschtest\Dragon_Hunters\Dragon_Hunters_-_Die_Drachenj?ger\2006-11-15.17.00.01.01.rec\001.vdr:554
main error: no suitable access module for `\\vdrserver\video\Loeschtest\Dragon_Hunters\Dragon_Hunters_-_Die_Drachenj?ger\2006-11-15.17.00.01.01.rec\001.vdr'

[md]

It looks like a problem with encoding during the HTTP transfer.

Could you please try to create the same m3u file in Notepad, and save it into two different
files using ANSI encoding for the first file and UTF8 encoding for the second file. Then try to
open these m3u files with VLC.

[Telepski]

German mutual vowels within m3u playlists still aren't recognized even in VLC 0.86 Beta version.

E.G. th line
'Geschüttelt nicht gerührt.mp3'

display shortly below in the VLSC status line as
'Gesch?ttelt nicht ger?hrt.mp3'

(See the question marks!)

The file is ignored and VLC jumps to the next line within the playlist.

During installation VLC has choosen the German language as default. So it knows about the system and its specialities, but it can't handle them.

Other players like e.g. WinAMP don't drive into those problems and play the same playlist without any problems.

When I try the hint of md and save the same playlist as unicode, ut works.

Thus it may be that VLC recognizes a system with a Non-English operating system correctly (e.g. during installtion) but does not recgnize the appropriate codepage?

By the way - saving as DOS text gives the already mentioned problems, mutual vowels (äöü) turn into question marks.

[md]

Thanks for the detailed bugreport. I've opened https://trac.videolan.org/vlc/ticket/862 to track this problem

[afrikaner]

These problems have been fixed recently - but only on Unicode-capable Windows versions
(NT,2000,XP,Vista)

Please try:

http://download.videolan.org/pub/testin ... -win32.exe

Thanks! Works for me now.

[md]

The bug with M3U playlists was fixed recently.
Please try http://nightlies.videolan.org/build/win ... -win32.exe

[The DJ]

remember it's a "best-effort"-fix it's definetly not foolproof

[thuety]

Sorry if this is off topic...
Just went from win32 0.8.5 to 0.8.6a, finally the japanese filenames work (smb and local)
Thanks a lot, you guys are great!!