[F] DevBuild: Tags in system default encodings?

bug-fixed

#1

There seems to be a problem with the newest Unicode-enabled Mp3Tag builds (2.32q) when using tags in system default encodings (cp1251 in my case). Here is a screenshot which illustrates the problem.

http://www.nncron.ru/temp/unicode.jpg

The filename and tags are in cp1251. Mp3Tag displays the filename correctly, but the tags (and FreeDB info) are displayed as garbage.

Is it possible to fix this?


Problems with tags in other languages
[F] DevBuild: Hebrew text in tag
#2

The support for system codepage encodings has been dropped (because of Unicode).
But I guess unfortunately, the freedb has lots of entries in local encodings (tho officially not supported! UTF-8 should be used.)
Maybe Florian wants to add an option to choose the encoding for freedb..


#3

I'm pretty sure there should be an option (or action?) which allow user to read the tags in a system default encoding to be able to save them back in Unicode (smth like 'Convert tags from local default encoding to Unicode').

Currently it is impossible to convert any of the available tags in local encodings to Unicode just because Mp3Tag can't read them properly...

Many other Unicode-enabled software (Foobar2000 as an example) works well with Unicode and with system default encoding at the same time.


#4

The current Development Build contains a new action type Convert codepage which converts the tag contents from the selected codepage to Unicode.

This feature is also available at the freedb dialog.

Hope this solves all issues. Thank you Valery, for your help!

Best regards,
~ Florian


[F] DevBuild: Hebrew text in tag
#5

I can't find it there (v2.33b). :unsure:


#6

Just go to :mt_act: Converter > Actions, create a new action group using the :mt_new: New-Button and create a new action Convert codepage within this action group.

Best regards,
~ Florian


#7

OK, thanks, but:

  • It's a very hidden feature, name for New conf. is confusing, I didn't know what to type there... I suggest to merge it with next window like this:

New configuration
Name: [.....]
Actions: [.....] [buttons...]

  • Problem is that I can't convert more songs at once since "correct" characters are converted too - and I loose special characters in these songs (bad songs are good and good are bad). :frowning:

Is it possible to add an option to convert just "bad/wrong" names/items? It is very complicated to distinguish "good" and "bad" songs, so I must do it all manually.


#8

No, this can't be done automatically.


#9
  1. What about ability to do not use unicode completely by an option:

[x] Use unicode

  1. If not possible, what is the last non-unicode version of Mp3tag and where I can download?

Thanks in advance.


#10

You can get the last non-unicode version from the download page.

Regards,
~ Florian


#11

OK, thanks, so option (above) is not possible to add? I'd like to use always the latest version with new features...


#12

I've just released a new Development Build which might solve your problems.

The new version has an option Decode ISO-8859-1 tags using system codepage at Options > Tags > Mpeg which forces Mp3tag to use the system codepage when reading ID3v2 tags.

Please note that your tags are automatically converted to Unicode format (which meets the ID3v2 standard), when you save them again.

Hope that helps!

~ Florian


#13

Thank you very much, it works good now (read and write). I think this option (Decode ISO-8859-1 tags using system codepage) should be enabled by default, since if it's disabled, tags are still converted to unicode, but incorrectly.

The problem is just Winamp, but I can wait for unicode version or find another one, since I don't like it much.

More important - before I'll convert all my songs/tags to unicode - what about mp3 and DVD players, will unicode tags look good/correct there?


#14

I'm glad that this option solved your problems :slight_smile: Though I won't enable it by default since ID3v2 tags in system default encoding are not standardized.

hint foobar2000 hint :slight_smile:

You have to try it. There are still some devices that don't support Unicode, but there are also good ones :slight_smile:

Best regards,
~ Florian


#15

OK, but I don't have DVD player, just in PC. How many, in % should support unicode? All (or most) new DVD and mp3 players should support it or just few? Thanks.


#16

The freedb dialog was rewritten in the latest dev. builds, and the Convert codepage feature is missed from the freedb dialog. If there is a chance to see it back?


#17

I usually don't like to put the same functionality at multiple places in the program and codepage conversion is already available as an action.


#18

I understand this, but still think we need a encoding conversion in freedb dialog: just to be able to choose the right freedb response. Without encoding conversion we may stay with smth like this:


#19

I won't add it for v2.40 anymore (which will be released this weekend), but I'll bring that option back with the next beta cycle.

(Note for testing: an example is folk, 210fa312)

Cheers,
Florian


#20

It's back again with the current Development Build v2.40a (see Utils menu).

Kind regards,
Florian