Bug 333745 - Amarok exports unreadable playlists for other players...

[Alan Ezust]

This is a change in the behaviour from previous versions of Amarok, however.
And it is possible to use different *encodings* for url when serializing or
de-serializing them.

So for example, if I wanted to convert the percent-encoding into a regular
path, I would use PyQt5:
decoded = QUrl.fromPercentEncoding(line);

This gives me the decoded version of the URL as a string, which can then be
understood by other programs and players, such as my blackberry phone.
Currently, it can not read amarok-generated playlists. While I realize that
technically, you are not supposed to have actual spaces in URLs, and while
URLs are supposed to be on each line of a .m3u file, m3u files have been
around for a very long time and programs that claim to read them do not
always play nice with this percent encoding that is used in more popular
players today.

I have noticed most players are not able to decode this percent encoding
and do understand spaces in playlists, so I do have to convert
amarok-generated playlists to this other format for them to be readable.

I wish there was an option to switch on or off this encoding feature.


On Tue, Mar 3, 2015 at 9:19 AM, Thomas Lübking <thomas.luebking at gmail.com>
wrote:

> On Montag, 2. März 2015 21:05:01 CEST, Brian Blater wrote:
>
>> On Mon, Mar 2, 2015 at 2:40 PM, Thomas Lübking <thomas.luebking at gmail.com
>> >
>> wrote:
>>
>>  On Montag, 2. März 2015 17:19:50 CEST, Brian Blater wrote:
>>>  ...
>>>
>>
>> It doesn't matter what I export it as (m3u, pls, xspf) it still contains
>> the inserted characters. My point being that this used to work and didn't
>> insert the characters before I upgraded to 14.04.
>>
>
> You missed the point: The file format does not matter.
> A URL *must not* contain spaces. Not from amarok nor anything else.
> There's nothing "inserted" - the URL encodes invalid characters.
>
> Therefore the first and foremost question is whether the entries in
> question are URLs or not.
> If they are, the behavior (whatever it caused) is correct, putting blanks
> in there would be a quirk for broken importers and the fix should really
> happen on the other client.
>
> However, I just tried and audacious (3.6) itself exports properly encoded
> URLs (ie. " " is replaced by "%20") in M3Us and has no problem with
> importing them either.
>
> => I suggest to provide a troublesome playlist.
>
>
> Cheers,
> Thomas
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok/attachments/20150407/6eb3ad6f/attachment.html>