russian letters
-
- Posts: 1
- Joined: 25 Jul 2015 13:38
russian letters
We are interested in your programm ProppFrexx Metadata Editor, but it can't decode russian letters. Is it possible to solve that problem? Thanx!
Re: russian letters
The issue is, that I see, that you are using WAV files. And they use the "RIFF INFO" chunk to store TAG data.
However, the standard of RIFF INFO defines Latin-1 as the encoding! And Latin-1 can not handle the Russian character set.
But...
...there is an option, if you open the general settings, go to the 'Tagging' section and click on the 'Extended TAG Options...' button.
There you'll find a "RIFF INFO UTF8" option - check this and the RIFF INFO data is stored in UTF-8 encoding, which can perfectly handle all character sets. This option is however disabled by default, as, as said, the standard defined Latin-1 for the RIFF INFO chunk.
You might also try the 'Broken Latin-1' option, which instead of using Latin-1 would use your computers default character set.
This option however would prevent your audio files TAGs from being read by any other computer not using that same character set.
Note, that for existing files you/I/the Tagger can not determine the original character set, so if the files have been written using an invalid tagger, which used a non-standard code page/character set (either Latin-1 NOR UTF-8) you might never be able to read them correctly.
However, the standard of RIFF INFO defines Latin-1 as the encoding! And Latin-1 can not handle the Russian character set.
But...
...there is an option, if you open the general settings, go to the 'Tagging' section and click on the 'Extended TAG Options...' button.
There you'll find a "RIFF INFO UTF8" option - check this and the RIFF INFO data is stored in UTF-8 encoding, which can perfectly handle all character sets. This option is however disabled by default, as, as said, the standard defined Latin-1 for the RIFF INFO chunk.
You might also try the 'Broken Latin-1' option, which instead of using Latin-1 would use your computers default character set.
This option however would prevent your audio files TAGs from being read by any other computer not using that same character set.
Note, that for existing files you/I/the Tagger can not determine the original character set, so if the files have been written using an invalid tagger, which used a non-standard code page/character set (either Latin-1 NOR UTF-8) you might never be able to read them correctly.
Bernd - radio42
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution
ProppFrexx ONAIR - The Playout and Broadcast Automation Solution