Usually WWWUSER is used in ID3v2 to store a url. If I set it using foobar it won't get recognized by Tag&Rename, a different program I use for tagging my stuff. However, it does get recognized by Winamp. If I use Tag&Rename to set the url, it gets recognized in all programs as a url and WWWUSER.

I realize it might be Tag&Rename related but I assume it's foo_id3v2.

I forgot all about this issue and now all my mp3's are kinda f*cked up...

I used foobar2000 to ReplayGain scan all my files and because of the tag rewrite I "lost" all my URLs in the mp3 files.
What could be the cause of the problem? Character encoding?
I tried 2 programs this time, Tag&Rename and The GodFather. After the tag rewrite in foobar both programs aren't able to recognize the info stored in the WWWUSER tag anymore. In Tag&Rename the tag is just empty and in The GodFather it display's only question marks.
It get's even worse with The GodFather. Unlike Tag&Rename, The GodFather also isn't able to read the COMMENT view anymore, this again will result in question marks only.
If I set foo_id3v2 to write ISO-8859-1 tags the problems do not occur.

I'd like to pin-point this issue in order to get it fixed.
Tag&Rename supports writing tags in Unicode (unknown which version though). So I assume I it should be able to read them as well. ;-) I wasn't able to find any Unicode options in The GodFather so I assume it hasn't got Unicode support.

The strange thing is that the problems do not occur with the other (default) ID3v2 tag fields (artist, title, album, genre, etc). Do these fields get written with a different character encoding?? :-S

Is there an easy way to check in the mp3 files which character encoding is used for the tags?

It might be possible that foo_id3v2 is writing the info to the wrong id3v2 "tag code", how can I check this in the mp3 file itself? Though this is a bit unlikely since it's all ok in ISO-8859-1. Also, this still won't explain why the COMMENT field can be read by Tag&Rename and not by The GodFather.

While typing this post I'm comming to the conclusion it's almost certain that the problem is the Unicode support in the other two programs but some confirmation would be nice to have before I start bothering them about it ;-)

As for fixing my files easily: I assume the best thing to do is to set foo_id3v2 to write ISO-8859-1 tags and rewrite all tags from the db to the file, isn't it?
The problem is that a small amount of files do need Unicode though...but I guess it's better than nothing...