Summary: | juk renaming file removes part from comment field | ||
---|---|---|---|
Product: | [Frameworks and Libraries] taglib | Reporter: | Marco Krohn <marco.krohn> |
Component: | general | Assignee: | Scott Wheeler <wheeler> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | micha |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Marco Krohn
2004-06-05 19:03:19 UTC
It seems this time bugs.kde.org didn't add the summary information: 2.0.81 (KDE 3.2.90 (3.3 alpha1, CVS >= 20040522), compiled sources) Linux (i686) release 2.4.23-1-k7 gcc version 3.3.3 (Debian 20040401) I can confirm this bug over here, although the it's not the Renamer's fault. From my testing over here, if you have a file that only contains an ID3v1 tag, then the comment field will be truncated after writing out to the file. You can confirm this by adding a comment, saving it, and then refreshing the tag. However, once JuK has written to the file, the next tag it writes will be in the ID3v2 format, which can hold a much longer comment. I'm pretty sure that JuK or the underlying taglib is supposed to detect when ID3v2 is necessary and switch automatically, but we'll probably have to have Scott investigate this further. This is a TagLib issue, so I'm moving it there. (And actively working on it at the moment.) CVS commit by wheeler: Provide a default (empty) value for the language. The lack thereof was was causing the bytes to not get lined up properly in the newly written tag and then they weren't read back properly. CCMAIL:82898-done@bugs.kde.org M +1 -1 commentsframe.cpp 1.19 --- kdesupport/taglib/mpeg/id3v2/frames/commentsframe.cpp #1.18:1.19 @@ -134,5 +134,5 @@ ByteVector CommentsFrame::renderFields() v.append(char(d->textEncoding)); - v.append(d->language); + v.append(d->language.size() == 3 ? d->language : " "); v.append(d->description.data(d->textEncoding)); v.append(textDelimiter(d->textEncoding)); |