Post reply

Message icon:

Unregistered users must pass a verification:

Please enter the number from the picture above which is showing FM broadcast antenna:

shortcuts: hit alt+s to submit/post or alt+p to preview

Topic Summary

Posted by: wbtcpip
« on: May 12, 2023, 06:30:00 pm »

thank you
Posted by: Jan
« on: May 12, 2023, 04:20:25 pm »

I've sent the conversion table to your email.
First word is the EBU Latin character (128-255), next three words are appropriate Unicode characters in hex representation. 0 means unused position.
Posted by: wbtcpip
« on: May 12, 2023, 02:12:50 pm »

ok thank you. For PIRA32 i'm cuurrently sending windows-1250 characters and apparently it works. It's more safe if i send 20127 us-ascii US-ASCII (7-bit) ?  (i'm using WideCharToMultiByte api call inside my application)
Posted by: Jan
« on: May 12, 2023, 09:20:43 am »

All current PIRA models (excl. PIRA32) accept UTF-8 via the XCMD= command:

Code: [Select]
XCMD=<rds><item><text>The RT here incl. řščěřžčžř and other extended characters</text></item></rds>
Code: [Select]

The receivers do not support UTF-8 via RDS and no such support is defined in currently applied RDS/RBDS standards.
The encoder or its control software internally convert UTF-8 to 8-bit EBU Latin code page.
The ability to show the extended characters depends on whether the character is convertible to EBU Latin code page.

[1] xcmd.pdf
[2] The RDS encoder manual, section 'Character Set and Code-Table Conversions'
Posted by: wbtcpip
« on: May 12, 2023, 08:33:55 am »

could you please confirm me if all RDS PIRA encoder models accept UTF8 characters in DPS1= DPS2= RT1= and RT2= commands? both via USB/COM or TCP?

If not, could you please tell me which models expect UTF8 charcaters and and which not?

thank you