Issue importing glossary csv file: characters are badly encoded

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	-
-	-	-	-	-	-	-

Supporter timezone: Asia/Karachi (GMT+05:00)

Tagged: ATE, Bug, Known issue

This topic contains 0 replies, has 0 voices.

Last updated by Waqas Bin Hasan 3 days, 6 hours ago.

Assisted by: Waqas Bin Hasan.

Author	Posts
January 22, 2025 at 8:53 am #16621550
alexandreP-37	Background of the issue: I am trying to import a glossary CSV file into WPML on my site hidden link. I have referred to the documentation on bulk importing and exporting glossary using CSV files: https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/how-to-create-and-manage-glossary-entries/#bulk-importing-and-exporting-glossary-using-csv-files. I also want to refer to a previous support ticket that was closed without confirmation: https://wpml.org/forums/topic/importing-a-glossary-in-csv-file-utf8-encoded-results-in-broken-characters/#post-16619851. Symptoms: The characters in the imported glossary CSV file are badly encoded. Questions: Why are the characters in my imported glossary CSV file badly encoded? How can I correctly import a glossary CSV file into WPML without character encoding issues?
January 22, 2025 at 9:53 am #16621911
Waqas Bin Hasan Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Hi, Reference to our recent chat, I've escalated the issue to our 2nd tier team for further investigation. I'll update you as soon as I have more information. Thank you for your patience and cooperation. Regards.
February 4, 2025 at 4:38 am #16664854
Waqas Bin Hasan Supporter Languages: English (English ) Timezone: Asia/Karachi (GMT+05:00)	Thank you for your patience and cooperation. Our team has published an errata at https://wpml.org/errata/advanced-translation-editor-special-characters-are-badly-encoded-when-importing-glossary/, where so far only solution is to creating glossary manually. However, the issue is in active development. I'll recommend subscribing to the comments of the said errata for any future update.