Bug 207504 - Taglib writes genre tags in a format itunes doesn't understand
Summary: Taglib writes genre tags in a format itunes doesn't understand
Status: RESOLVED WORKSFORME
Alias: None
Product: taglib
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources All
: NOR normal
Target Milestone: ---
Assignee: Scott Wheeler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-15 22:00 UTC by Michael Smith
Modified: 2023-01-08 05:16 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Add itunes hack for numeric TCON genres (2.01 KB, patch)
2009-09-15 22:00 UTC, Michael Smith
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Smith 2009-09-15 22:00:02 UTC
Created attachment 36975 [details]
Add itunes hack for numeric TCON genres

Taglib correctly writes ID3v2.4 TCON tags as numeric genres when possible; this is permissible and more compact that using the full text form.

However, itunes doesn't implement this correctly - it only understands the ID3v2.3 style numeric genres - which look like "(22)" as opposed to v2.4's "22".

The attached patch adds another itunes-hack to make taglib deal with this in a way that is both completely valid _and_ compatible with itunes..
Comment 1 Lukáš Lalinský 2009-09-17 09:58:26 UTC
This patch doesn't seem to be generated against SVN trunk. The code for dealing with '(22)Genre' looks a little different there. It will only add the numeric genre if it's different from the textual genre. I guess this ticket is about the cases when there is only the numeric genre, right?
Comment 2 Andrew Crouthamel 2018-11-02 23:01:24 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-16 05:23:57 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-09 22:13:17 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-12-24 05:23:02 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-01-08 05:16:17 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!