Post Reply 
reverseName handling for Composer tag
12-05-2014, 15:45 (This post was last modified: 12-05-2014 19:20 by simoncn.)
Post: #11
RE: reverseName handling for Composer tag
(12-05-2014 13:39)audio_elf Wrote:  I got that... But will have to retag everything! Which isn't the end of the word but if it's coming that it will work in the way I have (which was IIRC suggested by Simon) then I'm not going to leap in and retag everything!

I think you're referring to this post, which included the following:

Bach, Johann Sebastian (1685-1750) => Johann Sebatian Bach (1685-1750)
Gustavsen; Tord Gustavsen Trio => Tord Gustavsen Trio

The semicolon format wasn't suggested as a general convention but as a means of handling a few rare cases where standard name reversal of the desired sort value wouldn't produce the correct display value (e.g., Tord Gustavsen Trio). In the final implementation, I chose not to include support for the semicolon format because:

1) It is nonstandard (not supported by anything else), and I would prefer not to introduce a nonstandard format if there is a good standard alternative.

2) The situation where standard name reversal of the sort value doesn't produce the correct display value can be handed by populating both the Composer and ComposerSort (or Artist and ArtistSort) tags and setting the tagOptions and tagValue properties, as described in the User guide. This approach of using both Composer and ComposerSort (or Artist and ArtistSort) is standard and it provides more flexibility for tag customization and formatting than using a single combined string. The disadvantage is the need to populate two tags rather than one, but I don't think this should be a major issue if it's used only as an escape mechanism for rare cases.

I believe it would be possible to use regular expressions in Mp3tag to reduce the effort of retagging.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)