[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-09-19 19:21:45
Message-ID: 20050919192145.11560.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-09-19 21:21 -------
To Greg Meyer:

1.3 final (I have a build from kde-redhat on redora) still has _issues_ with \
encodings. Try editing a tag to contain non-latin1 characters, save, clean the \
playlist, than play that file again. Amarok cannot even load the tags it has just \
saved himself. This is just not acceptible, especially since it is all though \
Unicode.

I now have some (not too much, though) free time and would be willing to try and fix \
this, if someone cares to guide me a little though the tag-handling code of amarok. \
At least provide me with the list of file to look at or keywords to grep for. I \
actually read the mail for the address listed in bugzilla; I can try to hang on IRC a \
couple hour a day (around 20:00 GMT+4).

See my view of the problem above (comment 25 for this bug). I also propose:

a) explicit disabling of id3v1, via user-visible option. That's what 99% of people, \
who now have problems, would like, I suppose. At least, that's what I would like. And \
there's a wish report for it, I believe. b) explicit handling of id3v2 versions and \
encoding. With some sane defaults like 'v2.4 in UTF-16 with BOM' or maybe 'v2.3 \
UTF-16 BOM', to support older hardware MP3-players.  c) 'prefer v1 to v2' and 'v1 \
encoding is not latin1' should be clearly separated options. They certainly are \
useful in different situations. d) these should go onto a separate options pane like \
'MP3 tags options', with a worning of "don't touch unless you have problems and know \
what you're doing". e) Maybe (but in the distant future) fuller tag-editing \
capabilities, like 'strip v{1,2} tags', 'copy v1<->v2, per field', 'set tags from \
filename and vice versa', etc.


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