unicode capable id3 tagger ?

[gabor]

hi,

i cannot believe there aren't any usable unicode capable id3 taggers.

id3v2.3 can contain iso-8859-1 and utf-16.
id3v2.4 can also contain utf-8.

IS THERE ANY TAGGER THAT SUPPORTS THESE?

i went thru easytag, id3v2, id3lib....

is THERE ANYTHING USABLE?

(

can also be command line..


of course i have no idea about how well the mp3-player-programs (muine/rhythmbox/xmms) handle those tags, because I CANNOT CREATE THEM!


sorry for this angry message...i'm just sad that there's nothing usable there. it's inifinitively better with ogg files. they are utf-16 and that's it. no need for all this crazy stuff ...

[baeksu]

I believe Juk works decently with unicode. I`ve also used entagged, which is a java based tagger http://entagged.sourceforge.net/

Support for those tags is a little moody. I`ve seen amaroK survive them in the playlists, Rhythmbox also.
_________________
Gnome:
1. A legendary being.
2. A never ending quest to make unix friendly to people who don't want unix and excruciating for those that do.

[Schorsch]

Hi, I had the same problem - wanted to use cyrillic ID3 tags. Some minutes ago i found a java tool called "id3conv" which reencodes ID3 tags to unicode.

http://www.cs.berkeley.edu/~zf/id3iconv/

My current procedure to tag mp3 files with unicode looks like this:

• Tagging the file with a tagger like EasyTag
  
• java -jar id3conv.jar *.mp3
  

After using id3conv some taggers might have problems to display the correct tags - EasyTag displays nothing for example. But with the console tool eyeD3 you can proove, that the tags are correct (unicode tagging with eyeD3 didn't worked on my computer). Rhythmbox also displays the correct tags.

It's of course not very comfortable, but at least it works.
_________________
In theory there is no difference between theory and practice.
In practice there is.

[matroskin]

id3v2 works perfect for me. v2 tags set with it are coorectly visible everywhere/ checked with zinf, id3info, beep etc

P.S. i use utf8 for cyrilic chars mainly

[gabor]

the problem is that you might be able to enter utf8-encoded characters into your mp3s with id3v2,
but that's simply not correct.

the problem is the following:

the id3v2 data is saved in 'frames'. there are some text-frames, which contain textual data, and those which contain other thing.. like album cover and so on.

in the text-frames, the first byte says the encoding. the rest is the encoded text.

as i wrote previously, in id3v2.3 the encoding can be latin1 and two flavours of utf16.

in id3v2.4 you can use those from id3v2.3 and utf8.

so, the problem is, that when you do it with for example id3v2:
-it writes the utf8-encoded data into the text-frame, but the first byte still says it's latin1
-it does not increment the version number to 2.4 (which is needed because of the usage of utf8)

the reason why it works in the players you tried is, that they simply ignore the encoding specified in that byte.

if you try for example muine or rhythmbox or amarok, you'll see

btw. eyeD3 seems to work . so in case of id3v2, try to use eyeD3. (the newest version)

[matroskin]

eyeD3 fails to set any tag with cyrrilic chars. for example

[matroskin]

used eyeD3 0.6.3

[svyatogor]

hm, I got strange issue with eyeD3. When I give a command like this:

[gabor]

it means what it says

PLEASE read my previous comment, i described this already.

id3v2.3 can use latin1, and utf16.

id3v2.4 can use latin1, utf16 and utf8.

so either use utf16 or id3v2.4

[svyatogor]

[nicfit]

[placeholder]

The tag editor in Beep Media Player allowed me to add cyrillic to a tag, so perhaps that could be looked into.

[zbindere]

I use eyeD3 in a python script and I like it a lot.
Does anyone know how to force it to write with version 2.3 instead of 2.4?

*edit

Ok I found it. great tool.

[svyatogor]