View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004955||MediaMonkey (current)||Properties/Auto-Tools||public||2008-11-21 15:58||2010-12-17 01:04|
|Target Version||Fixed in Version||4.0|
|Summary||0004955: Ability to easily get rid of Non-Ascii characters when writing files|
|Description||There are a couple of problems with the current means of mapping metadata to filenames using FileMappings in the .ini file.|
1. Currently there isn't a way how to turn on this functionality just for some specific action. E.g. if I want to burn a data CD for a player that doesn't support non-ASCII characters, but otherwise I don't want to remap filename characters, then something like $RemapASCII function would be useful in burn filename mask.
2. Currently the functionality is hidden and hard to configure. E.g. for a common action of removing diacritics (e.g. for that CD burning) user would have to enter all characters of his national alphabet. Instead, we could hardcode such mapping to MM (we already do have such mapping e.g. in SQLite for full-text search) and so user wouldn't have to do anything in order to use such a feature.
Jiri suggested approaches to fixing this:
1) Add a new mask option $RemapASCII() to convert the bracketed section of the mask to ASCII characters based on similar mappings in MM used for full text search.
2) Add an option to [x] Map non-ASCII characters to ASCII
The first is probably simpler in the short term, though at some point we might want to consider adding either a bunch of flags or checkboxes on another panel for this and other options such as NoSpaces, etc.
Note: The functionality would not replace the current FileMappings .ini functionality, but rather augment it. i.e. $RemapASCII() would convert characters to their ASCII mappings, but would be overridden by any remaps specified in FileMappings ini config (it is still required to specify how to map characters like '*', which can't be part of filename but which _are_ valid ascii characters). The KB article would have to be revised to reflect this.
|Fixed in build||1301|
I would prefer Jiris first solution due the fact that second one could make confusion in tags & playlists -> ID3v2 options and also in WAV tagging which already have that INI setting for Forced ASCII tags.
Additionally it would be also better for us as we there will be less changes to HELP and UI.
Implemented function $RemapASCII() in build 1301.
Added todoc tag to be documented in help.