Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Foobar editing metadata with Japanese characters bug (Read 410 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Foobar editing metadata with Japanese characters bug

I copied the Japanese titles from vgmdb into the track title metadata field in foobar for an album. One title copied was クロノ・トリガー Jazz Arrangement (クロノ・トリガー), but when pasted into the field, it is displayed incorrectly. The dakuten, the two small strokes, in ガ at the end are displayed after the dash sign instead, so it becomes かー ゙. This seems to be purely a display error, because when I copy the wrong looking text from foobar into something else it looks correct again. I fixed it by pasting the characters in one by one, that made the text appear correctly.

The files were .flac files if it matters. I'm on Windows 11, set to English and my foobar is version 2.1.5 (x64).
 

Re: Foobar editing metadata with Japanese characters bug

Reply #1 –
It doesn't look a foobar2000 bug. Your first instance of the character ガ is that exact character, UTF-8 codes e3 82 ac. The next instance in the parenthesis is ガ, UTF-8 codes e3 82 ab (カ) + e3 82 99 (゙). They are differently constructed characters as their codes differ. They look the same when rendered with DirectDraw but not when rendered with GDI. I don't know how your browser shows the code e3 82 99, over here it escaped the parenthesis I placed it in and it's attached to the 'T' of the next word.

In Windows world it's typical to use the actual letter instead of constructing it from multiple code points. It takes less space and it's more correct to refer to the actual character as it is, it's even searchable without hacks when it's the right character. I was not aware of GDI font rendering having issues with some symbols but now I know.

This isn't foobar2000 bug because for example Windows Notepad (the old version, not Win11 store version that uses newer graphics APIs) renders it the same way. Notepad++ too, unless configured to use DirectWrite text rendering. FYI Columns UI alpha 3 uses DirectWrite and renders your character correctly.

I have made a component for sanitizing tag fields with the unnormalized unicode symbols. You can download it here: https://foobar.hyv.fi/?view=foo_tag_normalizer.

Re: Foobar editing metadata with Japanese characters bug

Reply #2 –
I see, that makes sense. Thanks for the explanation. I edited the online tracklist, too.