<track>
			<location>file:///H:/Media/M/World/Mali/Kagb%C3%A9%20Sidib%C3%A9/L%27Adieu%20%28Amazon%20MP3%29/01%20-%20Dougounalo.mp3</location>
			<title>Dougounalo</title>
			<creator>Kagbé Sidibé</creator>
			<album>L'Adieu</album>
			<trackNum>1</trackNum>
			<duration>385933</duration>
			<extension application="http://www.videolan.org/vlc/playlist/0">
				<vlc:id>15</vlc:id>
			</extension>
		</track>
		<track>
			<location>file:///H:/Media/M/World/Mali/Alou%20Fane%20et%20Daouda%20Sangare/Kamalen%20Ngonin%20%28Likembe%20MP3%29/b2.%20Nambaramogo.mp3</location>
			<title>Nambaramogo</title>
			<creator>Alou Fané et Daouda Sangaré</creator>
			<album>Kamalen N'gonin</album>
			<trackNum>6</trackNum>
			<duration>224448</duration>
			<extension application="http://www.videolan.org/vlc/playlist/0">
				<vlc:id>16</vlc:id>
			</extension>
		</track>

Hi, I'm using Media Monkey 4.1.11.1783 Standard Edition on Vista SP3
The XSPF import doesn't seem to handle UTF-8 sequences in the <location> URI field correctly.
For example, if there's a "LATIN SMALL LETTER E WITH ACUTE" in the URI (code point 00E9, rendered in the URI as %C3%A9), then the corresponding line in the "Now Playing" window renders the character as the sequence "LATIN CAPITAL LETTER A WITH TILDE" + "COPYRIGHT SIGN". The line is greyed-out, presumably because MM can't find the file. For example, in the following snippet, the first "record" fails to be imported correctly, but the second is OK, with the actute e's in the <creator> field rendered correctly:

[code]
<track>
<location>file:///H:/Media/M/World/Mali/Kagb%C3%A9%20Sidib%C3%A9/L%27Adieu%20%28Amazon%20MP3%29/01%20-%20Dougounalo.mp3</location>
<title>Dougounalo</title>
<creator>Kagbé Sidibé</creator>
<album>L'Adieu</album>
<trackNum>1</trackNum>
<duration>385933</duration>
<extension application="http://www.videolan.org/vlc/playlist/0">
<vlc:id>15</vlc:id>
</extension>
</track>
<track>
<location>file:///H:/Media/M/World/Mali/Alou%20Fane%20et%20Daouda%20Sangare/Kamalen%20Ngonin%20%28Likembe%20MP3%29/b2.%20Nambaramogo.mp3</location>
<title>Nambaramogo</title>
<creator>Alou Fané et Daouda Sangaré</creator>
<album>Kamalen N'gonin</album>
<trackNum>6</trackNum>
<duration>224448</duration>
<extension application="http://www.videolan.org/vlc/playlist/0">
<vlc:id>16</vlc:id>
</extension>
</track>
[/code]

This shouldn't be too hard to fix.

Following the links you're supposed to be able to open it with File > Open URL or File: http://www.ventismedia.com/mantis/view.php?id=5502#c18104

Was XSPF import ever added? I don't see it.

Also, has anyone discovered a way to convert XSPF to a format MM can read?

Excellent. Thanks Ludek!

Entered as http://www.ventismedia.com/mantis/view.php?id=6238

XSPF reading has been added in 3.2:
http://www.ventismedia.com/mantis/view.php?id=5502

I will create new issue for export.

I know this thread is old but native support of XSPF would be great. It is such a superior format to .M3U and the fact that is is XML means it can be validated and that XSLT can be used against it to transform your playlists into HTML pages or reports or just about anything you want. XSPF is really starting to become mainstream.

I know there is a script but I was hoping it would become native as Send To...->Export as .xspf Playlist option.

Just bumping this to add my vote. :)

Ok, the XSPF feature just moved up a couple of notches on my personal wishlist after discovering the site musicmobs.com. :lol:

There users can create and download XSPF playlists. Musicmobs developed an itunes plugin called Mobster. Mobster can match the tracks on such a playlist with songs you got in your itunes library. The matching could be a bit more fuzzy, but it's really neat.

I changed trixmoto's XSPF Creator script a little, so it produces XSPF files in the same format as Musicmobs. Even after changing the file pathes to something non-existent, Mobster matched the tracks on the exported playlist with the songs in my itunes library perfectly. Really cool!

I'd love such a XSPF import feature in MM too!

This most likely can be done with scripts (sorry didn't read the specs).

Great idea. I keep seeing XSPF support on a lot of social/web2.0 sites but I haven't really messed with it. This would be a very good motivator.

One thing I'm not entirely clear on, so I'm going on assumption here: In order for the thing to work, you have to have access to copies of the songs hosted online somewhere, correct? Like your own web server or something?

http://www.xspf.org/specs/

an open playlist specification