From: Peter Verthez Date: Sun, 20 Jan 2002 13:32:26 +0000 (+0000) Subject: General update of docs. X-Git-Url: https://git.dlugolecki.net.pl/?a=commitdiff_plain;h=544f96760b60a3f472442d8c9bc706d79411dd42;hp=465e8c27883cb6e9c4df526e91da9c7bc1a7b506;p=gedcom-parse.git General update of docs. --- diff --git a/doc/links.html b/doc/links.html index 6c32756..cf68827 100644 --- a/doc/links.html +++ b/doc/links.html @@ -1,12 +1,10 @@ GEDCOM links - - - + -

Useful links

-
+

Useful links
+

GEDCOM

The GEDCOM standard, release 5.5

xterm

testgedcom

gedcom

./testgedcom -dg t/ulhc.ged
+
./testgedcom -dg t/input/ulhc.ged

The -dg option instructs the parser to show its own debug messages (see ./testgedcom -h for the full set of options). @@ -100,10 +100,10 @@ containing a lot of special characters.

For the ANSEL test file (t/ansel.ged), you have to set the environment variable GCONV_PATH to the ansel - subdirectory of the gedcom directory:
+ subdirectory of the top directory:

export GCONV_PATH=./ansel - ./testgedcom -dg t/ansel.ged + ./testgedcom -dg t/input/ansel.ged
This is because for the ANSEL character set an extra module is needed for the iconv library (more on this later). But again, this should @@ -119,7 +119,7 @@ containing a lot of special characters.

make lexer_1byte
- This will generate a lexer program that can process e.g. the t/allged.ged + This will generate a lexer program that can process e.g. the t/input/allged.ged test file. Simply cat the file through the lexer on standard input and you should get all the tokens in the file. Similar tests can be done using make lexer_hilo and @@ -149,12 +149,20 @@ For each recognized statement in the GEDCOM file, the parser calls some callback which can be registered by the application to get the information out of the file. -This basic description ignores the problem of character encoding. The next section describes what this problem exactly is. +This basic description ignores the problem of character encoding. Character encoding Refer to this page for some introduction on character encoding... - -TO BE COMPLETED + +GEDCOM defines three standard encodings: + + ASCII + ANSEL + UNICODE (assumed to be UCS-2, either big-endian or little-endian: the GEDCOM spec doesn't specify this) + These are all supported by the parser, and converted into UTF-8 format. + + +

Useful links

Useful links +

GEDCOM

Character encoding

Useful links
+