For cross-platform compatibility, m3u8 uses utf-8 encoding (whereas m3u uses the creator system's default encoding).
I'm using the -musicPath='./' option to generate relative m3u files. I put them in the Media folder, and rsync the whole thing to my Android device.
But many entries in the playlists are broken due to special characters in either the filename or some folder in the path.
Some 'trivial' special characters like è are already problematic (I'm on mac, output is incompatible with android as you mention in the FAQ).
Using m3u8 and forcing utf-8 encoding for output should fix all encoding issues mentioned in the FAQ.
For cross-platform compatibility, m3u8 uses utf-8 encoding (whereas m3u uses the creator system's default encoding).
I'm using the
-musicPath='./'option to generate relative m3u files. I put them in theMediafolder, and rsync the whole thing to my Android device.But many entries in the playlists are broken due to special characters in either the filename or some folder in the path.
Some 'trivial' special characters like
èare already problematic (I'm on mac, output is incompatible with android as you mention in the FAQ).Using m3u8 and forcing utf-8 encoding for output should fix all encoding issues mentioned in the FAQ.