[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 89747] Issues saving new tags with recoded 8bit encoding
From:       "Alexey A.Kiritchun" <kaa () nightmail ! ru>
Date:       2005-02-18 13:39:21
Message-ID: 20050218133921.1303.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=89747         




------- Additional Comments From kaa nightmail ru  2005-02-18 14:39 -------
This affects me badly, as I am Russian.

My 2 cents on proper solution:

- id3v1 should be stored and read in the charset specified in options, or in current \
locale if option is not set. To make it clear, when reading, convert from 'charset' \
to UTF, and when writing, from UTF to 'charset'. If the latter loses some info, warn \
                user.
- There should be an option to disable reading and writing id3v1 altogether, and only \
                use id3v2. This should solve most of the problems. 
- id3v2 tags should _always_ be written in Unicode. There is no reason not to do \
this, and this is the easiest and least error-prone thing to do (fewer special \
cases), I think.

I can try and test whatever patches you would provide. At first I thought that I \
would patch it myself, but, alas, work with tags is scattered all over the code (or \
so it seems), and I could not see any 'scheme' behind it. My C++ got somewhat rusty \
(after 3 years of Perl), so the task turned out too difficult for me.


[prev in list] [next in list] [prev in thread] [next in thread]