On Mon, 2002-12-02 at 20:50, Don Allingham wrote:
> After several good comments both on the mailing list and some sent
> directly to me, I've think I've come to the conclusion that my original
> idea is not the best way to go.
> I think I have a better solution, mostly derived from the various
> comments. So, what I propose is:
> 1) Adding a new field in the name, which contains the name prefix.
> So, a person by the name of "Fred de Marco" would be classified
> Given Name : Fred
> Surname Prefix : de
> Surname: Marco
> 2) Provide a tool that will attempt to identify names with prefixes,
> and display the potential matches. The user can then select the
> ones that are correct, and fix any that were not extracted correctly.
> One suggestion that was made was to provide an additional field, that
> can provide pronunciation information. This is apparently valuable for
> languages like Japanese. The user would then have the option of sorting
> based off the surname or the pronunciation.
Hmmm... I wouldn't sort on a field intended for pronunciation
information. I would add a field called "sort by". Then whenever you
sort you would use the "sort by" information if present, otherwise use
However, I do like the idea of a field for pronunciation information.
It would also be nice to have a way to identify an audio clip as being
the person's name being spoken. A couple of suggestions:
1) Children should "inherit" the "sort by" and "pronunciation" data from
their father if they added as a new child to a family.
2) If a person's surname is edited, a dialog should pop up that should
give the user a choice:
A) Discard "sort by" and "pronunciation" information.
B) Edit the information.
C) Copy the information from someone with the same surname.
3) It'd be nice to have a tool that would propagate surname, sort by and
pronunciation information to a person's children, and potentially
recursively through male descendants. Even better would be to have a
dialog pop-up and offer to do this automatically if a this information