Author Topic: Language Problem in xmplay  (Read 8099 times)


  • Posts: 1
Language Problem in xmplay
« on: 2 Sep '03 - 16:54 »
I was trying to play an mp3 file, with name written in Cyrillic font (Russian) and the player could not read it. Once i rename it using English letters xmplay could play it. Is there anything I could do to make xmplay play files with names in other languages??? Please help, or I will be stuck using the discusting windows media player! Thankx.


  • Posts: 1242
Re: Language Problem in xmplay
« Reply #1 on: 2 Sep '03 - 17:15 »
Unfortunately, XMPlay doesn't support anything other than US-ASCII (I think.). Ian claims it supports UTF-8, but I haven't seen it work.


  • Posts: 1398
Re: Language Problem in xmplay
« Reply #2 on: 2 Sep '03 - 17:42 »
Even though there's no support for some languages, shouldn't the player still be able to play the files? Some kind of workaround would be nice, so that people wouldn't need to rename their files, just to be able to play them :).


  • Posts: 654
Re: Language Problem in xmplay
« Reply #3 on: 2 Sep '03 - 21:30 »
Well, MP3's ID3 system does NOT support unicode.  The tags are written in some Cyrillic code page or other, which translates into weird accented characters on a system whose Locale isn't cyrillic.

Ogg have full Unicode support (UTF-8 encoding in particular), and if the software supports that -- I'm not quite sure if XMplay does, in order to retain win9x compatibility -- those tags shall be displayed properly.

Blame MP3 :)

Ian @ un4seen

  • Administrator
  • Posts: 19625
Re: Language Problem in xmplay
« Reply #4 on: 3 Sep '03 - 12:31 »
I think the original poster meant funky characters in filenames, not tags.

Anyway, I'll see if anything can be done about it, without requiring a major re-write :)


  • Posts: 654
Re: Language Problem in xmplay
« Reply #5 on: 3 Sep '03 - 14:00 »
In that case, one thing you can do is to make the font follow system locale, and not force it to Western or something.
So if he's Russian, he'll see all accented characters (of filenames and mp3 id3) in cyrillic.

The other solution would require some sort of smart auto-detection algorithm, which will prolly fail a couple times (hebrew and russian codepages use a rather similar range of characters in the 0x80-0xff interval)

Third solution: extend playlist or .SET ("dotSET" la .NET ;D) with an option to save the file's locale (for the case of non-unicode mess, like old filesystems (FATxx), plain crappy filenames, ID3) and then, for that file, that decoding will be used by windows.
Like, you have the playlist, and the person set tahoma for pls area font: one file is in cyrillic or supposedly so, and we set that for later use in dotset, and then that one line will be FONT:Tahoma:n:8:Cyr, the others will be FONT:Tahoma:n:8:Wes since why would we default to anything else :)
For the case of Unicode stuff (properly named files in an NTFS file system, Ogg tags), I think displaying Unicode is not a problem in any post-95 Windows (i.e. 98 and above), but input of non-locale-range Unicode characters is not possible in non-NT systems.  The only place where we could need the input of weirdo Unicode characters is the Ogg Tag Editor.  The only thing displaying depends on is the fonts, but I'll gladly supply and host some free fonts that have 32000 glyphs if you guys need it :)