Yes, it was intentional as no other format is guaranteed to be reversible.
The problem is that one cannot know what character-set encoding is used by the file system. It need not be the same as that of the system locale. Therefore any kind of decode->encode process may mangle the pathname. I suppose that a *file:* URL may be presumed by some software to be in UTF-8 but I do not think that this is specified anywhere. There seems to be a fundamental conflict here: either a playlist can be written in a way that is guaranteed to be reversible by SbS given arbitrary filesystem pathname character-set encodings, or it can be interoperable with other software that makes some other assumptions about character-set encodings used for pathnames. Maybe the answer is to add another extension line, before the #EXTINF line, containing the *file:* URL, use M3U8 files and use UTF-8 encoding for the -normal- pathname. SbS would then prefer the new extension with the *file:* URL over the plain pathname. -- awy ------------------------------------------------------------------------ awy's Profile: http://forums.slimdevices.com/member.php?userid=7480 View this thread: http://forums.slimdevices.com/showthread.php?t=83641 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
