-
- <h2>Testing the parser with debugging</h2>
- Given the UTF-8 capable terminal, you can now let the <code>gedcom-parse</code>
- program print the values that it parses. An example of a command
-line is (in the <code>gedcom</code> directory):<br>
-
- <blockquote><code>./gedcom_parse -dg t/ulhc.ged</code><br>
+
+ <h2>Preparing for further testing</h2>
+ The basic testing described above doesn't show anything else than "Parse
+ succeeded", which is nice, but not very interesting. Some more detailed
+ tests are possible, via the <code>gedcom-parse</code> program that is generated
+ by <code>make test</code>. <br>
+ <br>
+ However, since the output that <code>gedcom-parse</code> 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.<br>
+ <br>
+ For the first issue, the UTF-8 capable terminal, the safest bet is to
+ use <code>xterm</code> in its unicode mode (which is supported by the
+ <code> xterm</code> coming with XFree86 4.0.x). UTF-8 capabilities
+ have only recently been added to <code>gnome-terminal</code>, so probably
+ that is not in your distribution yet (it certainly isn't in Red Hat 7.1).<br>
+ <br>
+ For the second issue, you'll need the ISO 10646-1 fonts. These
+come also with XFree86 4.0.x.<br>
+ <br>
+ The way to start <code>xterm</code> in unicode mode is then e.g. (put
+ everything on 1 line !):<br>
+
+ <blockquote><code>LANG=en_GB.UTF-8 xterm -bg 'black' -fg 'DarkGrey' -cm
+ -fn '-Misc-Fixed-Medium-R-SemiCondensed--13-120-75-75-C-60-ISO10646-1'</code><br>