by trinkner » Thu Mar 17, 2011 8:00 pm
After a lot of web research, I've given up using the accented Unicode characters in my tags. Sigh. I had hoped that MediaMonkey's character mapping would do the trick, but apparently not.
The chief reason I need the character mapping is the limitation of .m3u playlists, which are limited to ASCII characters. When I use MM to sync to my portable hard drive, it creates playlists, but it replaces the non-ASCII characters with odd symbols. My Squeezebox Touch, in turn, naturally can't find the playlist tracks because the characters MM inserts into the .m3u file don't match the filenames on the hard drive.
If anybody in the MM development team is reading this, it would be great if what appears to be a bug in the handling of the Filename Mapping feature of the .ini file could be fixed.
Ideally, at sync it would:
1. Use the character mapping when creating folder and file names on the synced device.
2. Adjust the file location specifications inside .m3u files accordingly
thanks
After a lot of web research, I've given up using the accented Unicode characters in my tags. Sigh. I had hoped that MediaMonkey's character mapping would do the trick, but apparently not.
The chief reason I need the character mapping is the limitation of .m3u playlists, which are limited to ASCII characters. When I use MM to sync to my portable hard drive, it creates playlists, but it replaces the non-ASCII characters with odd symbols. My Squeezebox Touch, in turn, naturally can't find the playlist tracks because the characters MM inserts into the .m3u file don't match the filenames on the hard drive.
If anybody in the MM development team is reading this, it would be great if what appears to be a bug in the handling of the Filename Mapping feature of the .ini file could be fixed.
Ideally, at sync it would:
1. Use the character mapping when creating folder and file names on the synced device.
2. Adjust the file location specifications inside .m3u files accordingly
thanks