Linux Special Character Encoding

[X X X]

Hi,

I recently updated Ubuntu from 18.04 to 20.04. At some point after updating the OS to 20.04, I recompiled TFS sources to change something related to PvP. After the recompile, I noticed certain characters were no longer displayed correctly in-game:



This changed even though I didn't touch anything in items.xml. Items.xml is encoded with ISO-8859-1 in the distro, and the item name is like so:

 <item id="5657" name="jalapeño pepper" article="a" plural="jalapeño peppers">
        <attribute key="weight" value="30" />
 </item>

The same thing happened to character names. There was a character with "å" in their name, after recompiling for the first time in Ubuntu 20.04, that letter was changed to "Ã¥" instead. Never made any changes to MyAAC or the database or anything.

I understand this has something to do with encoding and decoding; did the Ubuntu 20.04 update include different libraries or something?

​

 

[X X X]

Re-bumping this since I still can't figure it out. The database shows the special character correctly. The server terminal shows the player's name with the special character correctly when they log in. But in the actual client (CipSoft client or OTClient), it's all messed up:


Where does the player name get sent to the client?

 

[Perun]

you need to add font with special characters

 

[X X X]

I need to install the font to the OS itself?
-----------------EDIT--------------------
Maybe this is useful for someone who is more skilled than me,

I made a lua talkaction script to allow me to change my name in game. The script works, I changed the char name to "test". Then, when I tried to change it back, I get the following error in the game console:

Sår has logged in.
Sår has logged out.
test has logged in.
test has logged out.
[Error - mysql_real_query] Query: UPDATE players SET name = 'S\�r' WHERE name = 'test';
Message: Data too long for column 'name' at row 1

So the game server can understand the special character if it's coming from the database? But when the client sends the special character it is encoded wrong, it comes through as \�?