I remember a similar case where an emoji in an identity’s .ini file became a Unicode character and was not converted correctly from TS3 to TS5 when importing the identity.
I encountered another issue related to identity export and import in TeamSpeak 3.
When I export an identity from TeamSpeak 3 with unusual characters from font generators and import it into another TS3 client, the identity name and nickname are not imported correctly.
Case 1 – Identity name alphanumeric, nickname contains special characters
When I rename the identity with alphanumeric characters, but the stored nickname contains font characters, only the alphanumeric characters are imported correctly.
Case 2 – Both identity name and nickname contain special characters
If both the identity name and the saved nickname are not alphanumeric, neither name is imported.
Case 3 – Only alphanumeric characters
If the identity only contains alphanumeric characters, everything is imported completely.
Comparison with TeamSpeak 6
Okay, maybe it’s because of the non-alphanumeric characters. However, when I import the identity into the TS6 client, the generative characters are also imported entirely.
Additional information
To rule out localization issues, both TS3 clients were set to English. The issue still occurred.
No warnings or errors related to identities appear in the TeamSpeak 3 client logs during export or import.
Since the identity imports correctly into TS6, this suggests that the exported identity file itself is valid and that TS3 may have an issue handling (unicode- or) font generator characters during import.
TS6 allows importing identities, but I could not find an option to export identities. Therefore, I was unable to test exporting an identity from TS6 and importing it back into TS3.
OS: Windows 11
TS3-client: latest version
TS6-client: latest version
Regards
