1166 Illegal #EXTINFUTF token in Send to... .m3u... [6907]
Moderator: Gurus
1166 Illegal #EXTINFUTF token in Send to... .m3u... [6907]
...playlist
Send to... .m3u playlist can insert the illegal (i.e. non-compliant with original or extended m3u specification) #EXTIFUTF8 token e.g.
#EXTINFUTF8:149,Juan D'Arienzo canta Alberto Echagüe - Indiferencia
This is undesirable because it can cause failure of interoperation with other programs. If anyone knows of another publically-released program that is compatible with this token, please do say.
EDIT(TC): Tracked at http://www.ventismedia.com/mantis/view.php?id=6907
Send to... .m3u playlist can insert the illegal (i.e. non-compliant with original or extended m3u specification) #EXTIFUTF8 token e.g.
#EXTINFUTF8:149,Juan D'Arienzo canta Alberto Echagüe - Indiferencia
This is undesirable because it can cause failure of interoperation with other programs. If anyone knows of another publically-released program that is compatible with this token, please do say.
EDIT(TC): Tracked at http://www.ventismedia.com/mantis/view.php?id=6907
Chris
Winamp, I think.This is undesirable because it can cause failure of interoperation with other programs. If anyone knows of another publically-released program that is compatible with this token, please do say.
Extensions: ExternalTools, ExtractFields, SongPreviewer, LinkedTracks, CleanImport, and some other scripts (Need Help with Addons > List of All Scripts).
That's right, it will be fixed. I.e. from now on the only exception will be MediaMonkey.m3u in {AppData} folder, which _has_ to contain UTF-8 encoded paths in order to properly re-load Now Playing after restart.The option does work when the playlist save is requested by a plug-in and the Winamp-API. You still get #UTF8 entries after disabling this option. Please check. Thanks.
No, this option exactly means to do or don't include these extended lines (containing UTF-8 encoded info). The rest of M3Us is always plain 8-bit ASCII (according to the current codepage) due to compatibility.Thanks, but that has the unwanted side effect of disabling UTF-8 encoding!
Jiri
Jiri
Actually not, according to Options:jiri wrote:No, this option exactly means to do or don't include these extended lines (containing UTF-8 encoded info).Thanks, but that has the unwanted side effect of disabling UTF-8 encoding! ;)
[ ] Use Unicode (UTF-8 encoding) for M3U playlists
I'd really like it to do only what it says, since the problem I'm reporting is the non-standard token not the UTF-8. However I take it you've decided to disallow standard m3u format in UTF-8, so I'll work-around. Thanks.
Suggestion to coders: fix this checkbox label to accord with behaviour.
Suggestion to Help author: document this non-standard m3u format.
Chris
Well, there isn't anything like a 'standard m3u format in UTF-8'. M3Us are always in plain ASCII and that extension we added was an attempt to add Unicode support in as backward compatible way as possible. That said, for 3.1 we'll possibly add support for M3U8, which is a simple M3U, but in UTF-8. It's currently supported at least by WinAmp, but probably not by many other apps.
Jiri
Jiri
I beg to differ. The M3U spec doesn't prescribe the text file encoding and there's nothing wrong with ANSI (which MM and WinAmp do support) nor Unicode except apps haven't yet been coded for that.jiri wrote:Well, there isn't anything like a 'standard m3u format in UTF-8'. M3Us are always in plain ASCII
Shame that Winamp has made a new extension rather than just used BOMmed UTF-8 like the rest of the Windows world! ;)for 3.1 we'll possibly add support for M3U8, which is a simple M3U, but in UTF-8. It's currently supported at least by WinAmp
Chris
You certainly can store Unicode text directly to M3U, but you must start it with BOM, no matter which encoding is used (UTF-8, UTF-16 or whatever). This can certainly be easily done and is in some sense better that WinAmp's M3U8. However, compatibility issues make this solution a little problematic.I beg to differ. The M3U spec doesn't prescribe the text file encoding and there's nothing wrong with ANSI (which MM and WinAmp do support) nor Unicode except apps haven't yet been coded for that.
Jiri