Summary: | Writes unusable ID3v1 tags if metadata has non-Latin-1 characters | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | shattered |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | 1.4.5 | ||
Target Milestone: | --- | ||
Platform: | NetBSD pkgsrc | ||
OS: | NetBSD | ||
Latest Commit: | Version Fixed In: |
Description
shattered
2007-02-25 00:04:58 UTC
We won't do any encoding change ourselves. It's up to taglib to handle that, sorry. We've messed with id3v1 encoding in the past, and all we had was a great ammount of bugs here and there. SI'll mark this as a dup of the other bug. Consider this WON'TFIX as far as Amarok itself is concerned. *** This bug has been marked as a duplicate of 99149 *** amarok could strip v1 tag altogether in this case, no? ... like taglib author says (http://ktown.kde.org/~wheeler/taglib/api/classTagLib_1_1ID3v1_1_1StringHandler.html): "It is recommended that you not override this method, but instead do not write an ID3v1 tag in the case that the data is not ISO-8859-1." This has been recently fixed in taglib (SVN revision 768597) Great, thanks for the info. Still, released versions of taglib have the bug. Shouldn't amarok work around it? |