Thread: mp3 song title

Originally Posted by god_of_cpu

Non-standard characters will not display in Streetdeck.

What is standard? US-ASCII ? ISO-8859-1? Windows-1252?

Pim

Originally Posted by god_of_cpu

Non-standard characters will not display in Streetdeck.

THAT SUCKS! No Unicode support? You guys should definatly fix this problem!!!!!

It has been written elsewhere that StreetDeck
uses PNG images to display text, rather than
use Windows to render it.

So the source of these fonts would need to
make every character available as a bitmap
in order to fully support unicode.

Maybe this can be done if the fonts are rendered
from a TrueType or PostScript font, but I
don't know the origin of the fonts.

Edit: I see it's actually quite well documented in
StreetDeck Fonts

Unfortunately, the situation is worse than I expected:
there's only US-ASCII support, so even accented characters
will not display ... That really hurts!

Seeing this I suppose asking for Unicode is too much, but
can't you at least extend the character set to Windows-1252 ?

Pim

Originally Posted by pim

Unfortunately, the situation is worse than I expected:
there's only US-ASCII support, so even accented characters
will not display ... That really hurts!

Seeing this I suppose asking for Unicode is too much, but
can't you at least extend the character set to Windows-1252 ?

Pim

If there is a will there is a way! I'll look into the ".png" deal, there might be a way to get other languages into streetDeck. Because many of my song titles are in other languages. And would think more than 1/2 people that will use StreetDeck will be really disappointed about this fact.

Originally Posted by god_of_cpu

Version 1.0.4.5 will support ASCII charecters 32-256

That's great! But ASCII defines only characters 32-127. So the rest will be probably defined either according to iso-8859-1 (aka latin1) or windows-1252. Windows-1252 (aka Windows Western) is a superset of iso-8859-1; using that would enable a few characters (like curly quotes) that would otherwise only be encodable in utf-8 or utf-16.

It would be even better if the character set would be user selectable; for instance you would be able to load a font containg greek characters (above value 127) and have utf-16 encoded ID3 tags be translated to the character set corresponding to the font.

Doing so would enable almost any language, beit that only only language can be displayed correctly at a time without reloading a font.

Pim

Originally Posted by pim

That's great! But ASCII defines only characters 32-127. So the rest will be probably defined either according to iso-8859-1 (aka latin1) or windows-1252. Windows-1252 (aka Windows Western) is a superset of iso-8859-1; using that would enable a few characters (like curly quotes) that would otherwise only be encodable in utf-8 or utf-16.

It would be even better if the character set would be user selectable; for instance you would be able to load a font containg greek characters (above value 127) and have utf-16 encoded ID3 tags be translated to the character set corresponding to the font.

Doing so would enable almost any language, beit that only only language can be displayed correctly at a time without reloading a font.

Pim

For now just use TagScanner 4.9 Final:

http://www.free-codecs.com/download_...hp?d=230&s=160

It will allow you to change ID3 Tags from you native language into English translit automatically. Also you can batch rename files... etc

Originally Posted by debugger

It will allow you to change ID3 Tags from you native language into English translit automatically.

Are you suggesting I translate all my utf-8/utf-16/iso-8859-1 encoded tags, which display perfectly in every other application, to us-ascii, in order to suit a single broken application?

Pim