Latin letters wrong display

Hi everybody,

I live in France and am working in a french environnment.
My issue is quiet simple.
I have installed a config server (8.5.101.89) on a Linux VM (Red Hat Enterprise release 7.9).
The config database that the confg server use in installed on a SQL Server 2016 running on Windows 2016.
We use a odbc client on the linux VM to perform the connection : Microsoft ODBC Driver 17 for SQL Server

However, when the installation is over, on CME (or GA or GAX), we have a wrong display of character:

“é” - é

"Ã " - à

“û” - ù

“ê” - ê

“è” - è

“â” - â

“’” - ’ (apostrophe)

I have performed a test, by installing the same version of config server on a Windows VM, using the same config database, and everything is OK.

Did you configure locale on Linux system? If not, check what is the current value and change it to the proper one - I assume there is a conflict between locale and used encoding by Configuration Server. Also check whether you have enabled multi-language support on confserv level.

Thanks for your reply.
We have checked all these parameters.
All locale parameters on Linux are UTF-8

e.g LANG=fr_FR.UTF-8, LC_CTYPE=“fr_FR.UTF-8”, etc…

Also, the applicative user which starts the ./confserv is set with LANG=fr_FR.UTF-8

Did you also configure GA/GAX to support your encoding character set?

No, I didn’t.
Note that when I use the config server installed on a Windows VM, everything is fine.

PS: If ever, how do I configure the parameters you are talking about on GA/GAX?

GA - web.config
GAX - JVM parameter -Dfile.encoding

Hello everyone,

an official repsonse from Genesys:

“Non-Ascii characters are NOT supported by any version of Genesys on Linux. There is no plan/priority to address that, suggest customer to install DbServer on Windows.”

This is good to know.

Wait what? We have Genesys in full Linux with Brazilian characters working fine, we did adjustments to Encoding but that was it.
Or maybe yours is something different?

We are using Genesys with a SQL database installed on a Windows Server.
Maybe that’s the difference.

Check the collation of your SQL database. It matters for accentuation. Try Latin1_CI_AS