Your message dated Fri, 19 Jun 2026 23:14:52 +0200
with message-id <[email protected]>
and subject line Re: Bug#591045: id3v2 doesn't apply encoding correctly
has caused the Debian Bug report #591045,
regarding id3v2 doesn't apply encoding correctly
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.)
--
591045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591045
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: id3v2
Version: 0.1.11-3
id3v2 seems not to care about encodings at all. The ID3 Tag version 1
must always be ISO-8859-1, id3v2 applies the encoding used in the
terminal.
--- End Message ---
--- Begin Message ---
Already fixed, same charset-conversion work as #527157/ #559998 (NMU
0.1.12-2.1). Command-line text is interpreted in the system locale and
stored as ISO-8859-1 (or UTF-16 when needed) with the correct encoding
marker, so terminal bytes are no longer written verbatim; ID3v1 receives
proper Latin-1. I'm closing this bug report.
Martin
On Sat, Jul 31, 2010 at 13:58:35 +0200, Armin Fuerst wrote:
> Package: id3v2
> Version: 0.1.11-3
>
> id3v2 seems not to care about encodings at all. The ID3 Tag version 1
> must always be ISO-8859-1, id3v2 applies the encoding used in the
> terminal.
--- End Message ---
