> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/best-practice-guides/working-with-csv-files-in-excel-umlaute-and-special-characters.md). # CSV Files in Excel Encoding CSV Files in Excel with UTF-8 with BOM When working with CSV files and special characters, such as the **German *****Umlaute***, one has to be careful with opening those files in Excel, as often the special characters are not transformed correctly and are saved as such. This results in wrong formatting when uploading the CSV to a Locoia flow or any other system. As a solution, one should use [Sublime Text](https://www.sublimetext.com/) to handle such files and open them and then **Save with Encoding** > **UTF-8 with BOM**. This should preserve the "Umlaute" when you now open the CSV with Excel. ![Sublime - Save with Encoding - for encoding issues Excel](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48052589882/original/zKFyneCbtM1LTPkEJymrcqwhlbZtsSoRbg.png?1596648730) Also see encoding for [AWS S3 files](/connectors/connectors/s3-aws.md#s3-utf-8-content-type-encoding-of-files). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.locoia.com/best-practice-guides/working-with-csv-files-in-excel-umlaute-and-special-characters.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.