XXHighEnd

... like è, ë, ¢  etc., please keep in mind that those tracks currently won't make sound with Engine#3. You might have missed this in the release notes concerned ...

Obviously, depending on where you live, you may have these tracknames all over the place, and you will think *all* doesn't work.
I will try to have this solved in the upcoming weekend.

Poor freedb tags!  I hate them too! :grazy: I wrote a script that cleans up all my stuff.

It's amazing what developers have to cover to get a small piece of software up'n running! ;)

From that perspective, one could be impressed what MicroSoft has achieved to build a decent base (close to flawlessly) on all kind
of HW and SW and configurations. ( No, No -- I am not a fan of Microsoft! Forget that!  :grin: )

Cheers
Klaus

Just for fun ...

Officially this even can't be solved. The phenomenon "album- / tracktitles" is coming from the whole world to you, while you will use one "code page" (to type your own text etc.) hence the all over the world "typed" tracktitels can only be interpreted by their respective code pages. Unsolveable for practical reasons.

The stupidity here is that writing such "text" as a filename to disk *is* solved by the Windows OS. I'm not even sure how (and why exactly), but this will be related to the phenomenon "system string". All things go wrong when you write the same filename as data in memory or a textfile, which then has to be done in Unicode (allowing for just all characters from all over the world) but which needs interpretation "for which codepage" at reading back. The most stupid of it all is, that I don't really care what that russian trackname really means, but when the characters change on the way, the filename can't be found anymore (not in C++ and not without very ugly programming).

Ok, I solved it, but it could only be done with a big trick. :yes: