X-Git-Url: https://git.dlugolecki.net.pl/?a=blobdiff_plain;f=doc%2Fparser.html;h=4ff35cde9321cb3ee8bea78d852a1efa4c9742f2;hb=8c92a223c34fbd674f26520fb990c64a7b2f9147;hp=26586a36e6ec7ec4b6d70a0dca5a9064bc883a0d;hpb=8b7ff0dff0815a94ff08a9825d22a0c44490317a;p=gedcom-parse.git diff --git a/doc/parser.html b/doc/parser.html index 26586a3..4ff35cd 100644 --- a/doc/parser.html +++ b/doc/parser.html @@ -1,132 +1,124 @@
- + -- If everything goes OK, you'll see that some gedcom files are parsed, -and that each parse is successful. Note that the used gedcom files -are made by Heiner -Eichmann - and are an excellent way to test gedcom parsers thoroughly.make clean
- make
- make test
-
+ If everything goes OK, you'll see that some gedcom files are parsed, + and that each parse is successful. Note that the used gedcom files + are made by Heiner + Eichmann and are an excellent way to test gedcom parsers thoroughly../configure
+ make
+ make check
+
gedcom-parse
program that is generated
- by make test
. gedcom-parse
generates is
-in UTF-8 format (more on this later), some preparation is necessary to have
- a full view on it. Basically, you need a terminal that understands
-and can display UTF-8 encoded characters, and you need to proper fonts installed
- to display them. I'll give some advice on this here, based on the
-Red Hat 7.1 distribution that I use, with glibc 2.2 and XFree86 4.0.x. Any
- other distribution that has the same or newer versions for these components
- should give the same results.xterm
in its unicode mode (which is supported by the
- xterm
coming with XFree86 4.0.x). UTF-8 capabilities
-have only recently been added to gnome-terminal
, so probably
-that is not in your distribution yet (it certainly isn't in Red Hat 7.1).xterm
in unicode mode is then e.g. (put
-everything on 1 line !):- This first sets theLANG=en_GB.UTF-8 xterm -bg 'black' -fg 'DarkGrey' -cm - -fn '-Misc-Fixed-Medium-R-SemiCondensed--13-120-75-75-C-60-ISO10646-1'
-
LANG
variable to a locale that
-uses UTF-8, and then starts xterm
with a proper Unicode font.
- Some sample UTF-8 plain text files can be found
- here
- . Just cat
them on the command line and see the result.gedcom-parse
- program print the values that it parses. An example of a command
- line is (in the gedcom
directory):- The./gedcom_parse -dg t/ulhc.ged
-
-dg
option instructs the parser to show its own debug
-messages (see ./gedcom_parse -h
for the full set of options).
- If everything is OK, you'll see the values from the gedcom file, containing
-a lot of special characters.t/ansel.ged
), you have to set the
- environment variable GCONV_PATH
to the ansel
subdirectory
- of the gedcom directory:testgedcom
program
+that is generated by make test
. testgedcom
generates is
+ in UTF-8 format (more on this later), some preparation is necessary to
+have a full view on it. Basically, you need a terminal that understands
+ and can display UTF-8 encoded characters, and you need to proper fonts installed
+ to display them. I'll give some advice on this here, based on the
+ Red Hat 7.1 distribution that I use, with glibc 2.2 and XFree86 4.0.x. Any
+ other distribution that has the same or newer versions for these components
+ should give the same results.xterm
in its unicode mode (which is supported by the
+ xterm
coming with XFree86 4.0.x). UTF-8 capabilities
+ have only recently been added to gnome-terminal
, so probably
+ that is not in your distribution yet (it certainly isn't in Red Hat 7.1).xterm
in unicode mode is then e.g. (put
+ everything on 1 line !):+ This first sets theLANG=en_GB.UTF-8 xterm -bg 'black' -fg 'DarkGrey' -cm + -fn '-Misc-Fixed-Medium-R-SemiCondensed--13-120-75-75-C-60-ISO10646-1'
+
LANG
variable to a locale that
+ uses UTF-8, and then starts xterm
with a proper Unicode font.
+ Some sample UTF-8 plain text files can be found
+ here . Just cat
them on the command line
+and see the result.testgedcom
+ program print the values that it parses. An example of a command
+ line is (in the gedcom
directory):+ The./testgedcom -dg t/ulhc.ged
+
-dg
option instructs the parser to show its own debug
+ messages (see ./testgedcom -h
for the full set of options).
+ If everything is OK, you'll see the values from the gedcom file, containing
+ a lot of special characters.t/ansel.ged
), you have to set
+the environment variable GCONV_PATH
to the ansel
+ subdirectory of the gedcom directory:export GCONV_PATH=./ansel
- ./gedcom_parse -dg t/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
-show a lot of special characters.- This will show all tokens in themake clean
- make test_1byte
- cat t/allged.ged | ./test_1byte
-
t/allged.ged
test file.
- With the lexers you have to make sure that you use the proper lexer
-for each test file. The test_1byte
test program is OK
-for allged.ged
and ansel.ged
(the last one again
-with the environment variable set); for the uhl*.ged
files
-you need the test_hilo
test program; for the ulh*.ged
- files you need the test_lohi
program.t/allged.ged
test file. Similar
+ tests can be done using make test_hilo
and make test_lohi
+ (for the unicode lexers).$Id$+
$Name$