Posted by: Jan
« on: September 06, 2022, 08:38:11 pm »The conversion has been implemented in version 4.0.40. The options are available in the Virtual Port dialogue box.
News:
Thank you for using this forum as the technical support base for your device.
● You can format the text and attach screenshots, photos and RDS Spy records
● Faster reply: 50 % of questions are answered within 30 minutes
● You don't need to register (but registration is possible)
● The members represent a wide range of experts
● The resolution will be helpful to other users
● You'll be notified by email about new post
Posted by: nuno
« on: May 10, 2022, 10:22:18 pm »wow... thats will be a good thing...
do you have some prediction to implement that?
thank you
do you have some prediction to implement that?
thank you
Posted by: Jan
« on: May 10, 2022, 10:09:41 pm »No solution exists until we implement the character encoding selection.
Posted by: nuno
« on: May 10, 2022, 10:04:06 pm »Hi!
Any news about this? I have the same problem here. If I read from a text file output is ok but if I use TCP server I got weird characters at output.
How can we solve that?
Thank you for your help
Any news about this? I have the same problem here. If I read from a text file output is ok but if I use TCP server I got weird characters at output.
How can we solve that?
Thank you for your help
Posted by: Jan
« on: December 11, 2020, 12:31:46 pm »Yes, because you're sending the command in UTF-8 encoding, so ß results in two bytes: 0xC3 and 0x9F.
But the encoders usually work with EBU Latin code-table, so these two characters are displayed according to this table, see below.
The PIRA encoders accept UTF-8 if the text is entered from the web or using the XCMD=.
UECP encoders always need the EBU Latin encoding.
Other encoders may use proprietary codings and methods.
It is however a good idea to implement code table conversions for each virtual port. We will consider that for future version. The server itself is now fully transparent, it does not make any conversions. The Communication decoder expects EBU Latin for all commands excl. the XCMD=.
But the encoders usually work with EBU Latin code-table, so these two characters are displayed according to this table, see below.
The PIRA encoders accept UTF-8 if the text is entered from the web or using the XCMD=.
UECP encoders always need the EBU Latin encoding.
Other encoders may use proprietary codings and methods.
It is however a good idea to implement code table conversions for each virtual port. We will consider that for future version. The server itself is now fully transparent, it does not make any conversions. The Communication decoder expects EBU Latin for all commands excl. the XCMD=.
Posted by: m1k6
« on: December 11, 2020, 12:18:16 pm »Hello,
I'm configuring a bridge with TCP Server (so my application is a TCP client).
Using normal characters everything works as expected.
But I can't figure out the encoding of the TCP server.
For example if I send "RT=Außer Haus" Magic RDS reads "RT1=AuÈijer Haus"
I'm configuring a bridge with TCP Server (so my application is a TCP client).
Using normal characters everything works as expected.
But I can't figure out the encoding of the TCP server.
For example if I send "RT=Außer Haus" Magic RDS reads "RT1=AuÈijer Haus"