From: Eric N. <hic...@gm...> - 2005-11-15 18:36:31
|
As I see it, you want to have the support for either marking a portion of the given name as a callname, or supplying an additional callname and marking the portion of the given name that it should replace. For example, Richardus Bos would not want "Richard Richardus Bos" to appear on any report. He would want either "Richard Bos" or "Richardus Bos," depending on the report. And Lawrence Doe would not want "Lawrence Larry Doe" on a report, but either "Lawrence Doe," or "Larry Doe." Looking at it this way, a callname is an additional name that either IS one of the given names, or REPLACES one of the given names. This could be accomplished with 2 editable dropdown lists: Call Name: __________|v| Replaces Given Name: __________|v| [help] (the "|v|" is the dropdown box arrow) Both the Call Name field and the Replace field are editable dropdown lists populated with whitespace delimited substrings of the given name. Initially, the Replace field would be greyed out (inactive). First, you would either select the Call Name from the dropdown or enter in the Call Name. If the call name was entered in and not found as a whitespace delimited substring (whole word) in the Given Name field, the Replace field would become active. At that point, you could either select from the dropdown list or type in a substring of the Given Name field. The help button would explain all this, and explain call names in general. So, returning to Don's examples: 1) Donald Allingham, callname Donald. Select "Donald" in the Call Name dropdown. Done. 2) Richardus Bos, callname Richard. Type "Richard" in the Call Name box. Select "Richardus" in the Replace dropdown. 3) Lawrence Doe, callname Larry, Type "Larry" in the Call Name box. Select "Lawrence" in the Replace dropdown. Are there cases this doesn't cover? Is it an inadequate or confusing solution? Reports could use the given name and call name fields along with the call name replace string to do whatever they wanted with names. -Eric On 11/15/05, Don Allingham <don...@co...> wrote: > Unfortunately, the "select and mark" approach does not address all three > cases. While it may work for some areas of Europe (#1 and possibly #2), > it does not address the general case. > > Don > > Joachim Breitner wrote: > > Hi, > > > > thanks for the pointer. It seems to me that the "select and mark" > > approach would be best if we want to be able to export to that format > > later, at least better than the "repeat name in the Nickname field" > > approach. > > > > Greetings, > > Joachim > > > > Am Dienstag, den 15.11.2005, 07:07 +0100 schrieb Udo Vogel: > > > >>May I add a hint to a specification of a GEDCOM enhancement agred upon > >>by the Authors of genealogy programs Ages!, DYNAS-TREE, GES-2000, > >>GF-Ahnen, PC-Ahnen, GEDCOM 2 Map and the Society For Computer Genealogy= . > >>They suggest together following proposal of an extension of the GEDCOM > >><http://wiki-en.genealogy.net/wiki/GEDCOM> 5.5 standard called "Gedcom > >>5.5EL": > >> > >>http://wiki-en.genealogy.net/wiki/Gedcom_5.5EL > >>(refer to 'Names of a Person'). > >> > >>Udo > >> > >> > >>------------------------------------------------------- > >>This SF.Net email is sponsored by the JBoss Inc. Get Certified Today > >>Register for a JBoss Training Course. Free Certification Exam > >>for All Training Attendees Through End of 2005. For more info visit: > >>http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick > >>_______________________________________________ > >>Gramps-users mailing list > >>Gra...@li... > >>https://lists.sourceforge.net/lists/listinfo/gramps-users > >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. Get Certified Today > Register for a JBoss Training Course. Free Certification Exam > for All Training Attendees Through End of 2005. For more info visit: > http://ads.osdn.com/?ad_id=3D7628&alloc_id=3D16845&op=3Dclick > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |