Book Production in GEDitCOM II 1.7 - GEDitCOM II Discussions

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Book Production in GEDitCOM II 1.7
Received-SPF: pass (google.com: domain of egge...@verizon.net designates 206.46.173.21 as permitted sender) client-ip=206.46.173.21;
Content-type: text/plain; charset=us-ascii
MIME-version: 1.0 (Apple Message framework v1084)
Subject: Re: Book Production in GEDitCOM II 1.7
From: Jim Eggert <egge...@verizon.net>
In-reply-to: <931ED59A-A9BE-4BA4-A7E3-386B9913D17C@geditcom.com>
Date: Mon, 23 Apr 2012 01:35:18 -0400
Content-transfer-encoding: quoted-printable
Message-id: <7E5E0753-7DE6-4641-B42F-4A8061C919F3@verizon.net>
References: <ecfffb27-de84-4a87-9a2c-d806fb4e3f8d@t7g2000pbp.googlegroups.com>
 <0C04DD36-5FE5-4667-BB0C-ECE7B7D2CB56@verizon.net>
 <931ED59A-A9BE-4BA4-A7E3-386B9913D17C@geditcom.com>
To: geditcom-ii-discussions@googlegroups.com

On Apr 22, 2012, at 11:47 PM, John Nairn wrote:

> On Apr 21, 2012, at 10:40 PM, Jim Eggert wrote:
>=20
>> Here are some problems I have with Generations LaTex Book:
>> 1.  In running a descendants report, the descendants, though =
appearing in the proper generations, are in some arbitrary order within =
the generation.
>=20
> Each chapter is in aphpbetical order. All relatives are found and then =
grouped by generations. I wanted some order,but could not think of an =
obvious genealogical ordering, so they are listed in alphabetical order.

For ancestors, I would think ahnentafel order is appropriate.  For =
descendants, register order.

>> 5.  The wording introducing the sources for each person is awkward.
>=20
> I am open to suggestions (and fairly easy to customize in the script). =
My files tend to have all sources attached to events rather then the =
record as a whole. As a result, that wording does not appear often in my =
test books; they just appear as footnotes.

I can change it I suppose.

>> 6.  Backslashes aren't escaped.
>=20
> The script does escape them and it works for me. Do you have an =
example of where they are not escaped?

Backslashes don't work for me in surnames.  Maybe I shouldn't put =
backslashes in surnames.  How should I encode someone named John =
Smith/Jones?  (Not Smith-Jones.)

>> 7.  Not all Unicode in comments turn into TeX-friendly codes.
>=20
> A real limitation of LaTeX, unfortunately. Unicode is done be encoding =
the file in UTF-8 and then using the package:
>=20
>     \usepackage[utf8]{inputenc}
>=20
> But the documentation of this package admits it does not do all UTF-8 =
character. It seems to work well with characters found in names and =
places (i.e., any accented letters), but does not do well with =
non-letter characters and seems to completely fail with non-printing =
characters.
>=20
> The script has a list of bad characters and handles each as a special =
case. The other option is a different package, but I wanted something =
that would be part of the standard LaTeX install.

How about using XeLaTeX instead?

>> 8.  Unicode in source IDs messes up BibTeX.
>=20
> Source IDs (in GEDCOM sense) will never have Unicode. Do you mean in =
the text of the source citation?

No, I mean in GEDCOM IDs.  Maybe I shouldn't do that either!  So far =
GEDitCOM has let me get away with it, but I can fix it.

=3DJim
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
