I implemented a report statement done at global scope
which will cause any variable used before being set (or globall'd)
to be flagged as an error. Someone suggested this to me this
summer, but I cannot now recall whom.
How about if I change "z" (for zip browse) to "zi" (for zip browse
to indis), so as to make room for analogous ones for other types of
Is anyone using LifeLines to edit event GEDCOM, or at any rate, using
events ? Event lists (seen from browse/events) still don't carry any
summary information -- what would be appropriate there ? The tag
from the "0 EVEN Tag" line ? Plus the level 1 name and/or role lines
if present ?
Having modified the affected string functions to support UTF-8,
I could also modify them to work with ANSEL, if it is actually being used --
but is it ?
Get latest updates about Open Source Projects, Conferences and News.