Transform UTF-8 to Unicode in Echolink

Asked

Viewed 82 times

1

In the Echolink Server configuration file

/etc/svxlink/svxlink.d/ModuleEchoLink.conf

we can insert the location of the radio station in the LOCATION variable.

As the name of my city (Petrópolis) has accent, whenever I correctly write the name in the configuration file, it appears modified in the Echolink App (Client) as follows:

Petrópolis

It seems to be the eternal problem between Unicode and UTF-8.

I used the following site to try to convert in such a way that the "oh" appeared in the correct way: https://www.branah.com/unicode-converter

And in fact, when I write Petrópolis in the text area "UFT-8 text" appears the following result in the text area "Unicode text": Petris.

However, when I select and copy the Unicode text, something changes, because when pasting the copied text (Ctrl + C) in the configuration file and restart the server, we see that in the client Petrã³Polis turns into something like Petró[][][]Polis. That is, something happens in the direction we want to take (the accent appears), but it’s still not 100% correct.

Any tips on how to solve this problem? And besides, what do they call these coded squares () that appear in the online converter? Knowing the name, I can continue researching about.

Thank you!

  • 1

    To my knowledge UNICODE is a theoretical standard and has several implementations, one of them is UTF-8 (8-bit Unicode Transformation Format), so there is no point in talking about "transforming UTF-8 to Unicode). Probably is wrong specification of the encoding actually used.

  • 1

    So how to understand all these online possibilities of converting Unicode to decimal, text, url, etc?

  • Usually this type of error occurs when you configure that the default used is UTF-8 but sends text in another encoding, for example LATIN1 or ISO-8859-1. Set your environment properly and ensure that the characters are effectively encoded in the pattern you claim to be in. Note that this does not happen with the characters of the ASCII table because the first 127 characters of the UTF-8 standard are exactly the same as those of the ASCII table.

  • The problem is that there is no way I can set up a closed software environment. That’s why I’m trying to enter the variable value of the server configuration file (svxlink-server) already with the encoding it uses in the client (mobile app).

No answers

Browser other questions tagged

You are not signed in. Login or sign up in order to post.