Version: svn trunk (using KDE Devel) Installed from: Compiled sources OS: Linux Currently, amaroK set the encoding used to phrase id3v1 tags through its preferences. But it might not be user-friendly in its first startup. Furthermore, it is very difficult to preset the default value of "Recode Encoding" setting in mutilingual distro like Mandriva, because amaroK uses meaningless number rather than string to store encoding :( GStreamer has populated[1] a environment variable GST_ID3_TAG_ENCODING used to phrase the id3v1 tags. It would be better amaroK can detect it in its first startup, then set "Recode Encoding" accordingly. Of course, users can select another encoding in the future, but it would be a good start if they needn't touch it :p Note, it is only a enviornment variable, so it is not required that gstreamer engine be installed or selected by amaroK. [1] http://bugzilla.gnome.org/show_bug.cgi?id=149274#c17
tag recoding has been removed from amaroK too many associated problems with it.
IMHO, removing tag recoding completely is a really bad idea. That means, amaroK 1.4 can only be used by people who are using latin languages. GST_ID3_TAG_ENCODING is a good choice than nothing, especially when using gstreamer backends.
Your humble opinion has been noted, but we won't change it. Sorry.
For the record, the recoding option was for working around incorrectly tagged music files. So amaroK can still read and write non-latin languages.