CSV export Arabic language
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2024 07:33 PM
We have installed Arabic OOTB plugin for translation. The Excel export is working as expected. But the CSV export is not getting translated and the Arabic words are morphed into '?????'.
we have tried the below 2 options. Both are not working.
Option 1: system property "glide.export.csv.charset" to UTF-8
Option 2:
1. open up a blank Excel sheet.
2. Click on Data.
3. Click on Get Data and select 'From text'.
4. select the file which you wish to open.
5. On the next tab Change the File Origin to (UTF-8).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2024 12:29 AM
Hi @58288,
Before I get into problem solving, my first question would be - is there a need to export into a Spreadsheet?
The reason I ask is, if you are using the "Localization Framework" you should be able to either add the translations in the Comparison UI, or leverage one of the various integrations either to an MT (if you have one) or a TMS (if you have one). Generally speaking, with regards to translations, it's not a good practice to perform / action them etc via spreadsheets due to the limitations of Excel and other similar tools (and that's before considering file format limitations with CSV files),
Many thanks,
kind regards
Director of Globalization Deployment, Internationalization
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-28-2024 07:51 PM
Hi Alex,
Thank you for the response. The data is not being processed into any of the integrations. Its for end user consumption and they require the CSV export.
Thank you & Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2024 06:37 AM
Hi @58288,
It sounds like it might be a side-effect of where-ever you are creating the translations (where the CSV file is being processed). Are you using the Localization Framework or are you making some sort of custom spreedsheet exports? And would you be able to explain a bit more of how you're generating this CSV export?
Like I suggested above, CSV is really not the best way to perform translations as there are numerous challenges with that approach.
Many thanks,
Kind regards
Director of Globalization Deployment, Internationalization
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2024 03:28 AM
Hi Alex,
Thank you for the response.
Background on the issue: We have enabled new plugin Arabic in our environment. French, German are already available plugins activated in the system.
From the Sys_user table, if we are doing a OOTB CSV export, when the user's language is French, the export contains correct French language with no symbols. In the same way if we export with a user whose language is Arabic, then we are getting '???' in the place of Arabic.
We have not made any configuration changes in the Localization Framework .
If we are setting the system property "glide.export.csv.charset" to UTF-8 and then performing the steps in option 2, then the file is getting converted to Arabic.
Also once the property is set if we open the exported file in notepad, it displays Arabic.
But once the property is set, the initial export of both Arabic and French has symbols. we need to manipulate the data to make it available as Arabic/French.
KB: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0953658
But now without any of these manipulations, the French, German works fine.