Your message dated Fri, 19 Jun 2026 23:04:06 +0200
with message-id <[email protected]>
and subject line Re: Bug#527157: id3v2: written data depends on system locale,
which can lead to corruption
has caused the Debian Bug report #527157,
regarding id3v2: written data depends on system locale, which can lead to
corruption
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
527157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527157
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: id3v2
Version: 0.1.11-3
Severity: normal
When I want to set a tag, the text provided in the commandline is written
unmodified. This leads to data corruption if the system locale is not
latin1 (or ISO 8859-1). My system is set to UTF8 locale, so that the
following happens:
$ id3v2 --TIT2 "test" 07\ -\ Parties\ in\ München.mp3
Now let's see what a reliable tool (eyeD3) shows:
$ eyeD3 07\ -\ Parties\ in\ München.mp3
[...]
ID3 v2.3:
title: test artist: Superpunk
Now I set the real title of the track, which contains a german umlaut:
$ id3v2 --TIT2 "Parties in München" 07\ -\ Parties\ in\ München.mp3
And this is the eyeD3 output:
$ eyeD3 --debug 07\ -\ Parties\ in\ München.mp3
[snip]
eyeD3 trace> FrameSet: Reading Frame #6
eyeD3 trace> FrameHeader [start byte]: 91 (0x5B)
eyeD3 trace> FrameHeader [id]: TIT2 (0x54495432)
eyeD3 trace> FrameHeader [data size]: 20 (0x14)
eyeD3 trace> FrameHeader [flags]: ta(0) fa(0) ro(0) co(0) en(0) gr(0) un(0)
dl(0)
eyeD3 trace> FrameSet: Reading 20 (0x14) bytes of data from byte pos 101
(0x65)
eyeD3 trace> FrameSet: 20 bytes of data read
eyeD3 trace> TextFrame encoding: latin_1
eyeD3 trace> TextFrame text: Parties in München
[snip]
ID3 v2.3:
title: Parties in München artist: Superpunk
The UTF8 data from the terminal was put into the ID3 tag, which is wrong in
2 points:
1. the charset is set to latin_1
2. ID3 v2.3 doesn't support UTF8, only UTF16
If the user wants to put correctly encoded data into the tags, he/she has to
make sure to convert it to the correct encoding (latin1). He/She seems to be
completely lost if the input data contains characters which are not present
in the latin_1 charset.
Regards,
Tino
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-rc4-00187-gb4348f3 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages id3v2 depends on:
ii libc6 2.9-10 GNU C Library: Shared libraries
ii libgcc1 1:4.4.0-3 GCC support library
ii libid3-3.8.3c2a 3.8.3-7.2 Library for manipulating ID3v1 and
ii libstdc++6 4.4.0-3 The GNU Standard C++ Library v3
ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime
id3v2 recommends no packages.
id3v2 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Already fixed. The command-line text frames are written through id3lib's
charset-aware path (SetID3EncText), which interprets input in the system
locale and stores it as ISO-8859-1 when representable or UTF-16
otherwise, with the correct text-encoding marker. This is the write-side
counterpart of #559998 and was fixed by the charset-conversion patch
NMU'd in 0.1.12-2.1, so no raw locale bytes are stored mislabelled as
Latin-1 anymore. I'm closing this bug report.
Martin
On Mon, Apr 22, 2013 at 04:27:49 +0200, Mark J. Nelson wrote:
> fixed 527157 0.1.12-2.1
> thanks
>
> I believe this is essentially the "write" version of the "read" problem in
> bug #559998, and both should be fixed in the patch recently NMU'd in
> 0.1.12-2.1.
>
> The charset issues are overall still pretty poor, though. Since both id3v2
> and id3lib upstreams have been dormant for years, I believe the Debian
> maintainer (Stefan Ott) was planning to port id3v2 from id3lib to taglib,
> which is maintained upstream and handles charsets in a sane way. But I'm not
> sure what the status of the port is.
>
> Best,
> Mark
>
> --
> Mark J. Nelson
> IT University of Copenhagen
> http://www.kmjn.org/
--- End Message ---
