As I understand Lame.exe still does not understand unicode filenames!!!!!!!!!!!!!!!! Unbelievable!!!
At least under Linux the LAME frontend understands unicode in UTF-8 encoding. On Windows it doesn't matter much, because Windows Users do use GUI programs and seldom come in touch with a commandline shell. So, it'll be a nice to have feature, we might add later.
Delirium! I'm developer of audio comverter under windows. I use lame.exe to encode files via stdin. lame.exe doe not understand unicode filenames. I'm Russian,so I use russian localized windows, but I need to encode for example J'y Suis Jamais Allé.wav. To get out J'y Suis Jamais Allé.wav BUT NOT J'y Suis Jamais Alle.wav I have to say Lame encode J'y Suis Jamais Allé.wav , but it does not understand J'y Suis Jamais Allé.wav filename because of "é". To encode it I have set up French for programs which do not understand unicode, or trim "J'y Suis Jamais Allé.wav" to ansi "J'y Suis Jamais Alle.wav". Now you understand me ?
The problem is not in frontends, the problem is in the lame.exe, it does not understand unicode file names. Not read,nor write.
Two possible solutions:
1. Write to a non-Unicode temp file and rename it to the correct file name later.
2. Use the GetShortPathName API function to retrieve the non-Unicode 8.3 filename of the file you want to write to.
I recommend using method 1, because short filename support can be disabled for NTFS filesystems and therefore is not guaranteed to be available.
I do not see any need to add Unicode filename support to Windows LAME.
"add Unicode filename support to Windows LAME." would be the shortest and logical way to resolve this problem... But anyway of course thank you for advice, it seems I'l use "1. Write to a non-Unicode temp file and rename it to the correct file name later." variant as universal and the simplest :-)
LAME 3.99 has some experimental unicode support for Window builds. Some feedback is welcome.
There was no feedback, so I'm assuming unicode filenames work now as expected, closing this item.
Log in to post a comment.