It is very inconvienient if without codepage conversion plugin when dealing with non english songs.
This is an extension of the foo_masstag, and is pretty much the same as the foo_codepage_action plugin for the old foobar2000, but this is for 0.9.x.

the two extra functions are:
- codepage conversion
- conversion between simplified and traditional chinese

This plugin has been renamed to foo_masstag_addons, feature requests are welcome.

* read my blog for the dependency requirements before downloading *

current version: 0.3.4

change log

0.3.4
- added a new action: “Embedded cuesheet inserter”

this is an action to automatically insert the related cuesheet to the file, currently only: *.ape;*.tak;*.flac;*.mac are supported.

this is developed when I convert my APEs to TAKs, the operation is:

C:\album.cue
C:\album.tak

load album.tak to fb2k and put it to the masstagger, and select the action, then run

the action will:
1. put data of album.cue to album.tak as embedded cuesheet
2. remove the actual album.cue file (only will remove if the operation is sucessfully done)

0.3.3
- codepage combo boxes items are sorted now, it was auto sorted in xp, but in vista, it is a mess.

0.3.2
- multi-instance support for the conversions, now mutiple actions of the same type is supported

0.3.1
- minor bugs fixed

0.3
- chinese conversion is also included with the codepage conversion, you can now do the two actions in one step.
- the names "current cp" and "target cp" are changed accordingly.
- conversion preview added, you don't need to worry about messing up your tags by selecting wrong codepage anymore.

0.2.3
- allows user to specify the which meta data to convert

0.2.2
- allows user to select the current codepage

A little tutorial
codepage conversion now allows user to select the codepage currently used to dislay and the
codepage to convert.

this let user fix those files tagged by foo_freedb2, which treats any tags retreived from the
server as utf-8, but in fact the tags could be something else.
to fix these files, user selects iso-8859-1 as the displayed codepage and the correct codepage
as what user thinks it should be (this can be known if user browses the freedb website with the DISCID).

the displayed codepage and correct codepage are not your operating system's codepage, but the
codepage used to store in the actual file when it is not unicode (utf16) and utf8.
but for other files not tagged by foo_freedb2, the displayed codepage is most likely your windows
current code page.

in fact for any mis-tagged files, user just needs to known the codepage in the files and
the correct codepage to get them fixed, unless the files really have incorrect tags.

nobody uses it at all?

I'm sorry, I don't really have a use for this. Not really into non-English songs. I'm sure someone will. Good job though.

Thanks for the plugin, been waiting for sth like this for a while. The only problem now I found is I have to install the MSVC8 runtime lib.

How does this work? I see that it is similar to the special show file info plugin for 0.83. What tags does this plugin convert the codepage? All three of ID3v1, ID3v2.4 and APEv2 currently supported by foobar2k 0.92? I have my MP3 encoded in Chinese GBK but the portable MP3 player only recognizes ID3v2.3 UTF-16 encoding. I guess it is out of question for me to use the plugin to convert the codepage since foobar2k now saves the tags in ID3v2.4 and there is no UTF-16 encoding at the codepage conversion (only UTF-7 and UTF-8).

no, it is similar to the foo_codepage_action plugin in 0.8.x.
this plugin in fact doesn't know what tag it will convert, because it just changes the codepage of the text from meta info, so the tag type really depends on the tag type you've chosen of the input file.

Also, it has nothing to do with ID3v1, or whatever. The main purpose of the conversion is converting the meta info text which is from other codepage such as big5, gbk, to utf-8.

The primary reason I write this plugin is because I have many mp3 using GBK in the tag, but I'm using Big5 windows, the text shown in foobar is garbage (you know what I mean, I think).
I need a plugin like this to convert the text so it can be displayed properly in my big5 windows (both simplified and traditional can be displayed).

Thanks a lot, I do have to go thru the codepages manually a lot for Chinese songs, I'll try it out

So is it useless to convert text displayed originally in a wrong encoding?

I don't know what you mean by "originally in a wrong encoding", but I can give you another example.

if you have a japanese song using S-JIS as its tagging codepage, but you are not using a japanese windows. the meta info displayed in your foobar will probably be empty (blank) or garbage text. You can use this plugin to convert the text with codepage 932 to utf-8, the text will then be properly displayed.

K this thing works like a charm! Way better than having to go thru in individualy, thanks !

Hmm...i have the same problems like yours.
but i'm wondering...
if i get the tags from freedb.org is in gbk encoding.
and i use the codepage action which plugged into foobar2000 0.8.3(i don't like 0.9.x..)
i choose convert simplified chinese into traditional chinese.
it worked..and the tags displayed perfect.
but i have a question...
the tags aren't in utf-8, are they?
how do i make sure the tags will be using traditional chinese characters in utf-8 library?
because when i use utf-8 to utf-8 using masstager...the tags just become a bunch of `?'

thanks

you are confused with the old codepage_action plugin, I was, also.
the action of codepage conversion is converting the tagged file from the codepage to utf-8, while simplified to traditional chinese conversion is in fact utf-8 to utf-8 conversion.

to avoid '?', you need to be aware of what the tagging character set is, bascially, if you see the garbage text, you should have 2 conversions, first for codepage to utf-8, second for simp. to trad. conversion.
if you can see the simp. chinese before doing any conversion, you just need the sim. to trad. conversion.

Thanks for this gr8t plg-in. It's what I need.

Thank you for replying to my post.
but i still have a few questions.
i have files with tags in garbage texts.
but i don't know which code set it originally using..
how do you know that?is there any program that can identified the code page the tags or filenames is using?
or i have to convert in order to check if i'm right?
i mean this when the tags of the album can't be found in freedb database.

question 2.
i know foobar can directly tag mp3 files from freedb.
but there's a problem.
i get into the `get tags from freedb' page.
and i have to choose a code page that in preview will show more correct information.
``hope you know what i'm saying...like choose gbk and it shows the tags with correct simplified chinese instead of garbage codes...''
and i tag it.
but here's the question..
after i tag it....foobar shows the simplified chinese information...
but is the tags in utf-8?
how do i know?
(when i use codepage conversion...i choose utf-8 to utf-8...it becomes a bunch of question marks...ha..)

is there anyway to know what code page the tags of the known few tagging system, id3v2, flac tags, ape tags,.etc or the files' names in windows are using? or even just check if they're using utf-8

BTW...
I would really like to know more about code page....
any books recommended if i want to do code page conversion or identification programming...
i know there's a o'reilly book about unicode...
just hope to get some advice from people who are already doing this kind of things...

hope you all know what i'm trying to say...
(my english is not very good....)
thanks for your patience

also...
if anyone is also using the program Convertz...
i have a question...
i have some files with names with unicode simplified chinese and unicode japanese..since they only show right in unicode preview..
when i want to convert the unicode from unicode simplified chinese into unicode traditional chinese, unicode japanese will disappear..and if i actually do the conversion...the unicode japanese couldn't be recovered after the conversion.
i thought every unicode version contains the same things...
then why when i do conversions between unicode and unicode traditional chinese(that is..in Convertz...i do unicode to unicode traditional chinese), if there are characters in unicode japanese it will disappear after the conversion.
but the unicode japanese characters will show good when in unicode simplified chinese...(that is ...in Convertz i choose unicode to unicode simplified chinese.)

i wonder...

you will not know, you have to guess to check.

if you can see the simplified chinese correctly in foobar, then it is already utf-8

I don't understand what you mean, or you can pm me in chinese

I have no idea.

I'm having the same problem with convertz, so I guess traditional chinese doesn't have the japanese characters.

brilliant component, i have TTPlayer, convertZ, and pagecode just to settle my problem with encoding..


.traditional chinese dont support japanese, use simplified instead, i am using jis for my self

btw, i cant download the archieve...

I've just checked, the download link is valid, what do you mean?

i guess my firefox have some issues, sorry for the inconvenients

are we suppose to click on the word binary to download?

yes

Hmm..

I downloaded the zip of the binary and copied the dll into foobar components.

however, i get this:
Failed to load DLL: foo_masstag_addons.dll

i have foobar 0.9.2 and masstager componen installed.

any ideas? :S

Download and install Microsoft Visual C++ 2005 runtime here or .NET Framework 2.0 if u need it.

Wow, this is a lifesaver.

I migrated from 0.83 to 0.9, and there's quite a big of files that I tagged using GB2312 (Simp. Chinese) - using the built in XP Language typing.

However, when I migrated to 0.9, the files' metadata was not recognized. Your plugin saved me..

PS: Does foobar only recognize only Unicode formatting, and not the rest? If I click on the file properties with Explorer, I can still see the metadata there...

so how do i know which codepage to use to get my korean songs showing?

Korean versions of Windows are likely to be in cp949. Maybe you should use 949.

Okay I am quite confused at what is up with my foobar in its abilities to display foreign characters. I've tried pretty much all the codepages to no avail. My foobar seems to be able to show some of the tags properly while other's don't work. Any help would be great.

Heres a picture of what I mean

screenshot

You can see it displaying the korean in the BAND field just fine. Doesn't want to work in the others though :/

Moderation: Please refrain from inlining images larger than roughly 800x600 and 80KB. Please use thumbnails and/or links for large pictures instead.

Maybe it was tagged and retagged by people from and outside of Korea. Maybe it was tagged and retagged using different programs.

That did the trick. I retagged the tracks and everything works perfect. Thanks

updated, put this on top of the forum......

In other words, the new codepage conversion will act like this: If the files have shift-JIS encoding then I chose in the current codepage shift-JIS and the target codepage UTP-8 right?

no.

if your file is tagged by foo_freedb2 and you found it is messed up. what you should do is:
current cp = 28591 (iso-8859-1)
target cp = 932 (Shift-JIS)

for any other situations you need to know the tag that wrongly used as the current cp (most likely this time is your windows current code page), and the correct code page as the target cp.

you don't have to select utf-8 as the code page at all.

Sir, after using this plug-in, i can see the Chinese Tags now
but there are spaces in the Japanese Tags
what can i do?

I am using Chinese Traditional winxp without HKSCS or Unicode-at-on

Excuse me. I have installed foo_masstag-addons, but I see no where I can change the current/target cp.
I also installed "MICROSOFT VISUAL C++ 2005 RUNTIME LIBRARIES"
Would you give a screenshot link to indicate where I can modify those cps?

In masstagger manage scripts there're two new action types.

context menu -> Tagging -> Manage Scripts -> Add -> Addon: Codepage conversion

I tried to use this addon to convert chinese traditional (big5) to unicode
but The result tags are still rubblish characters

My existing mp3 tag is written masstagger in fb0.8.3

I selected current CP is 950 (ansi/oem traditional chinese big5)
and traget CP is 65001 (UTF-8)

is thatn right ?

It would be great if the plugin allowed to specify which tag to convert, as it's unusable for me as it works now. Some of my files have tags using multiple codepages, so if I try to correct one tag (ie. LYRICS) others (ie. ARTIST) gets borked.

@adrianmak
firstly, unicode virtually is utf-16.
secondly, you can't convert it to unicode (utf-16).
the purpose of this functionality is to get the tag displayed properly, not for converting to other codepage, in fact.
whatever user selects the current_cp and target_cp are just the in-between codepages for the conversion, the ultimate codepage will always be utf-8, which is
foobar internally uses. I show you the concept here:

1. input tags are utf-8
2. conversion of codepages (convert to raw ascii by the current cp, then map to the target cp)
3. output tags as utf-8

now you should understand why you can't convert to unicode.

@LordWarlock
now you can specify the meta name to convert, as you wish.

Thank you for this component! Now that I've actually started downloading some J-Pop (and after reading the quoted post), I can successfully convert these broken JIS characters into Japanese Unicode characters!

Just a suggestion for future versions: Change "Current codepage" to "System codepage", and "Target codepage" to "File's codepage", so that it is easier to understand the component.

thanks for your suggestion, I will change the names, I couldn't think of the proper names for those two
but "current cp" to have a name "system codepage" probably not always correct, because for the situation of a file tagged by foo_freedb2, it is not the system codepage but the current wrong codepage of the file.

the names are changed, more suitable.
also, the important feature, conversion preview is added.

Thanks Acropolis, you rock, I have been waiting for the preview feature.

thank you, glad you like it.

This is plain super!! I have very long sought such software, I had found only the little command-line Java utility id3conv, which was far from what I need, especially because files with foreign characters in their names cannot be used in the command line (AFAIK). For at least a year, I put up with not viewing the tags of my Russian music. Sadly nearly everything is tagged incorrectly. Now all my problem is solved in a few minutes, thank you!

Hi... I'm really eager to try out the Masstagger Addon but the server is down...

before the server comes back, get it here:
http://www.hydrogenaudio.org/forums/index....showtopic=48927

EDIT: thanks to VaCUm, now my files are on his server, check the first post for the download link.

I can't seem to access your new page, Acropolis. It links to a page basically covered with ads with web tips or something.

Rofl nevermind, I didn't see your last post.

Would anyone beable to tell me how to get greek songs to show up correctly in foobar? I got a couple of CDs in Cyprus and when I load them up in with freedb in EAC or foobar it just comes up with wierd symbols. They work in iTunes, so I ripped them in iTunes although when I put them into foobar they just came up like "???????". What does iTunes use ISO 8859-1? And foobar uses UTF-8? I assume foobar reads ISO but prefers UTF because it is superior? Forgive me if I am talking a whole load of crap, I don't understand all this UTF ISO binary stuff.

If I rip the Greek CDs in iTunes then run this conversion tool, will that work? I don't really understand so please be patient with me. Plus with my iPod beable to show the Greek songs in their proper formatted tags in their proper Greek alphabet?

Thanks, Dave.

If someone has problems with cyrillic characters, here are my working settings:

Displayed codepage: 28591 (ISO 8859-1 Latin I)
Correct codepage: 1251 (ANSI cyrillic)

Maybe someone can help me here, I think I have some serious misunderstanding of what should be done. The situaton:

- I have a CD from Dir en Grey, a japanese band. Now I want to tag that CD with freedb, to get the japanese track titles. After I do that, the display in foobar of the tracks is garbled, I only see some squares instead.

- I now go to the masstagger, and set the first field to: ISO 8859-2 for my own german windows xp and then I set the second field, the correct codepage field to: 932 Shift-JIS.

- Now the squares disappear, but they are replaced with "???".

Can somebody try and help me ?

displayed codepage = 28591 (iso-8859-1)
correct codepage = 932 (shift-jis)
if this doesn't work, either your display font's problem or the tag is really incorrect.