From b9c095918e435dd995ac4282c277745924e366bd Mon Sep 17 00:00:00 2001
From: Cole Greer <112986082+Cole-Greer@users.noreply.github.com>
Date: Mon, 30 Oct 2023 09:51:55 -0700
Subject: [PATCH] Add text encoding example to readme (#78)

---
 README.md | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/README.md b/README.md
index 2b6481e6..e9b91e67 100644
--- a/README.md
+++ b/README.md
@@ -123,6 +123,12 @@ For large datasets, we recommend running this tool against a standalone database
 
 The latest version of _neptune-export_ uses the [GraphBinary](http://tinkerpop.apache.org/docs/3.4.0/upgrade/#_graphbinary) serialization format introduced in Gremlin 3.4.x. Previous versions of _neptune-export_ used Gryo. To revert to using Gryo, supply `--serializer GRYO_V3D0`.
 
+### Character Encoding
+
+_neptune-export_ attempts to use the JVM system default text encoding for all output files. This can be configured manually if needed by setting the `file.encoding` system property.
+
+```java -Dfile.encoding=UTF8 -jar neptune-export.jar ...```
+
 ## Exporting the Results of User-Supplied Queries
 
 _neptune-export_'s [`export-pg-from-queries`](docs/export-pg-from-queries.md) command allows you to supply groups of Gremlin queries and export the results to CSV or JSON.