Better handling of PAF double dates.

[gedcom-parse.git] / data / gedcom.enc

diff --git a/data/gedcom.enc b/data/gedcom.enc
index 4645be9811af61b04e3bcbdadbee4f1f5534207e..559473f2dc39d93a405163c1d4b1e6bc9bb3112c 100644 (file)
--- a/data/gedcom.enc
+++ b/data/gedcom.enc
@@ -3,17 +3,20 @@
 
 # Mapping of charsets for gedcom parsing
 # Each line contains (separated by whitespace):
-#   - the gedcom name
+#   - the gedcom name (with space replaced by underscore)
 #   - a token identifying the width of characters and the ordering;
 #     currently supported values: 1, 2_LOHI, 2_HILO
 #   - the iconv name of the charset
 
-# First the encodings supported by the GEDCOM standard
-UNICODE                2_LOHI  UNICODELITTLE
-UNICODE                2_HILO  UNICODEBIG
+# First the encodings supported by the GEDCOM 5.5 standard
+UNICODE                2_LOHI  UCS-2LE
+UNICODE                2_HILO  UCS-2BE
 ASCII          1       ASCII
 ANSEL          1       ANSEL
 
 # Then some very frequently used non-standard encodings:
 # Note that CP1252 is a superset of ISO-8859-1, so that is covered too
 ANSI           1       CP1252
+IBM_WINDOWS    1       CP1252
+# The following is explicitly allowed in the draft 5.5.1 GEDCOM standard
+UTF-8          1       UTF-8