Handle new " / " from taglib 2.0 #12854
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…and comment as well)
…to sort out encoding issues.
|
This need some good testing. @Holzhaus can you have a look since you use Taglib 2.0 in you build environment? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #12790 by ignoring the new multi value separator when comparing tags.
After installing taglib 2.0 this separator will populate the Mixxx database when reading a multi value tag.
After editing such tag, the multi values are deleted and the new value is stored a singe Tag containing the " / " separator.
This is a workaround to allow to use Taglib 2. Writing full multi value tags is more work.