Data merge is not importing certain characters correctly. Namely greek letters (Ψ, Ω, etc). I've tried different fonts and still no dice.
5 Answers
Found the solution here. The trick was changing the encoding on the .csv to UTF-16
-
Great, it works with changing the encoding to UTF-16 with Sublime text editor by File > Save with encoding. After that I selected ASCI as import in Indesign, or is as UNICODE better? Commented Oct 4, 2022 at 13:45
I was able to successfully load Japanese characters by:
- save the data file as .csv in excel
- take that excel doc and uploading it to google sheets (to remove all the junk excel puts in their .csv)
- Redownload the file from google sheets. locate the file and (on windows) right click the file and hit "edit".
- This opened the file in Notepad, hit "save as" and change the encoding to "Unicode"
- load the new text file in Data Merge
I hope this helps anyone who may be googling around looking for a solution!
-
Excel doesn’t put any ‘junk’ in CSV files. It offers very little choice (read: none at all) by way of encoding and delimiter character, and it tends to quote columns that don’t need quoting, but none of that is ‘junk’. Uploading to Google Sheets is completely unnecessary, just open the file in a proper editor – don’t use Notepad, use something like Notepad++ or VSCode which give you actual control over the output and support CSV as a format, rather than just as plain text – and save with the appropriate settings. Commented Aug 12, 2020 at 6:50
If you save the Excel file as a Unicode file, you get what is essentially a tab delimited file. Take the file into Notepad or your favourite text editor and do a search and replace for the tabs and any extra spaces to each side and replace them with commas. You might need to do this two or three times to get the commas everywhere they need to go. Then save as "All Files ." and change the extension to CSV. Bada bing! The full Unicode set of characters will be preserved.
-
Whether it's tabs, commas or semicolons is irrelevant. All three types of delimiters are accepted. You don't need to save it as a .CSV either, a .TXT will do. It's an encoding problem, not a delimiting or extension problem. Commented Jul 3 at 15:26
I had the same issue. UTF-8 encoding gave garbled text when there were non-ascii characters, and indd couldn't handle UTF-16.
I opened the CSV in VSCode, and resaved it with Western (Windows 1252) encoding.
It's not perfect: Hagåtña comes in OK, but Kandahār fails.
I'm using InDesign 17.0.1 x64.
-
InDesign can handle UTF-16. UTF-8 doesn't cause any problem for the CSV file alone, but InDesign can't interpret it and that's where the garbling happens. Make sure to use UTF-16. Commented Jul 3 at 15:24
After hours of struggling, I've finally found a solution.
- DO NOT export with Excel. It doesn't offer encoding options, and it will garble your non-ASCII text. It really sucks. Use it only as a convenient tabular editor.
- Get Notepad++.
- InDesign accepts any .TXT or .CSV file. So just create a new file in Notepad++ and copy your entire spreadsheet to it. Select all, copy, paste, simple as that.
- IMPORTANT: Find "Encoding" on Notepad++'s menu bar. Choose either "UTF-16 BE BOM" or "UTF-16 LE BOM". "UTF-8" is what causes problems for most people, so make sure it's not chosen.
- Save your file as a simple .TXT file. Don't bother wasting your time with .CSV.
-
The format of the file (.txt, .csv, etc) is not relevant. Only the encoding matters. Commented Aug 4 at 16:46