{"id":7282,"date":"2026-01-14T14:54:59","date_gmt":"2026-01-14T21:54:59","guid":{"rendered":"https:\/\/support.spatialkey.com\/?p=7282"},"modified":"2026-01-23T15:17:31","modified_gmt":"2026-01-23T22:17:31","slug":"foreign-language-characters","status":"publish","type":"post","link":"https:\/\/support.spatialkey.com\/foreign-language-characters\/","title":{"rendered":"Foreign Language Characters"},"content":{"rendered":"

SpatialKey supports a wide range of languages and characters in datasets uploaded as CSV files. In most cases if the data looks right on your computer before uploading, it will appear correctly in SpatialKey. However, this doesn’t always produce perfect results. There are some manual steps you can take to ensure the best support for the full range of characters in your data.<\/p>\n

\"Example<\/a>
Example with Japanese characters<\/em><\/figcaption><\/figure>\n<\/p>\n

What bad data will look like<\/strong><\/h2>\n

If you are working with a dataset in SpatialKey and see data that either shows a square icon or question marks (Windows) or a diamond with a question mark (Mac) then there was a problem with the CSV upload. These errors can often be fixed by saving the CSV file with a specific character encoding.<\/p>\n

\"Example<\/a>
Example with invalid characters<\/em><\/figcaption><\/figure>\n<\/p>\n

<\/a>Encoding needed if using Windows XP\/7\/8<\/strong><\/h2>\n

You can use Notepad, which comes as a core application with Windows, to save the proper format.<\/p>\n