Author Topic: sending UTF8  (Read 3061 times)

wbtcpip

  • Newbie
  • *
  • Posts: 3
sending UTF8
« 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

Jan

  • Hero Member
  • *****
  • Posts: 1088
Re: sending UTF8
« Reply #1 on: May 12, 2023, 09:20:43 am »
All current PIRA models (excl. PIRA32) accept UTF-8 via the XCMD= command:

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

Notes:
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.

References:
[1] xcmd.pdf
[2] The RDS encoder manual, section 'Character Set and Code-Table Conversions'

wbtcpip

  • Newbie
  • *
  • Posts: 3
Re: sending UTF8
« Reply #2 on: May 12, 2023, 02:12:50 pm »
ok thank you. For PIRA32 i'm cuurrently sending windows-1250 characters https://learn.microsoft.com/en-us/windows/win32/intl/code-page-identifiers 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)

Jan

  • Hero Member
  • *****
  • Posts: 1088
Re: sending UTF8
« Reply #3 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.

wbtcpip

  • Newbie
  • *
  • Posts: 3
Re: sending UTF8
« Reply #4 on: May 12, 2023, 06:30:00 pm »
thank you