From: Nick H. <nic...@ho...> - 2010-08-10 16:23:07
|
Doug Blank wrote: > On Tue, Aug 10, 2010 at 9:30 AM, Peter Landgren <pet...@te...> wrote: > >> Den Tuesday 10 August 2010 15.12.00 skrev Doug Blank: >> >>> On Tue, Aug 10, 2010 at 8:57 AM, Peter Landgren <pet...@te...> wrote: >>> >>>> Den Tuesday 10 August 2010 13.21.09 skrev Doug Blank: >>>> >>>>> On Tue, Aug 10, 2010 at 4:46 AM, Peter Landgren <pet...@te...> >>>>> >>>>> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> >>>>>> >>>>>> I found the two options: >>>>>> >>>>>> "Use callname for common name" >>>>>> >>>>>> "Use full dates instead of only the year" >>>>>> >>>>> I don't know about the date option, but Name Formats now have an >>>>> >>>>> option that subsumes the first: you can define a Name Format that uses >>>>> >>>>> the callname if there is one, otherwise it uses the first part of the >>>>> >>>>> given name. It is called "Common" in the name format editor. So, I >>>>> >>>>> think you can remove the first option. >>>>> >>>> No, I don't think so. >>>> >>>> By NOT using the callname option you get: >>>> >>>> 1. LANDGREN, Per Albin Henrik (Albin). >>>> >>>> Per Albin Henrik was born on 1867-03-11 in Skeppsholmen (AB)[1a, >>>> >>>> 2a]. He died on 1947-01-04 in Nacka (AB) at the age of 79 >>>> >>>> By using the callname option you get: >>>> >>>> 1. LANDGREN, Per Albin Henrik (Albin). >>>> >>>> Albin was born on 1867-03-11 in Skeppsholmen (AB)[1a, 2a]. He died >>>> >>>> So this version looks better IMHO in stead of repeating all given names. >>>> >>> I see. So this is really a choice between: >>> >>> ( ) use the full given name in text >>> ( ) use the callname in text, if available >>> >> Yes. >> >> >>> We could reuse the NameDisplay code here, by providing a Name Format >>> Pattern for use in this place. That way we wouldn't duplicate this >>> common name code, and give more flexibility to users. For example, >>> people could also use the full name, initials, given name (callname), >>> or any other variation defined by the name format code. >>> >> I think it's a good idea make it more flexible. >> So, in stead of a check box it would be a drop down menu with name format codes? >> > > That's one way. Another way would just make it a Text Entry, and let > users type in the format directly, like "Given (Call)". That way, it > can be created on the fly. (I'll look into seeing if that is even > possible... it may be with the current system, it must be > pre-defined.) > A drop-down list of name formats would probably be better. The user would probably want to define a name format anyway, and I don't think that it would be unreasonable to require this. It would also be easier to select from a list. Nick. > -Doug > > >> /Peter >> >> >>> -Doug >>> >>> >>>> /Peter >>>> >>>> >>>>> -Doug >>>>> >>>>> >>>>>> a little bit confusing, see: >>>>>> >>>>>> http://www.gramps-project.org/bugs/view.php?id=4160 >>>>>> >>>>>> >>>>>> >>>>>> I took a look at the full date option and it seems not to used >>>>>> anywhere? >>>>>> >>>>>> It's easy to fix within DAR and DDR, but most dates are handled by >>>>>> >>>>>> libnarrate.py, where it's not used. Not as far as I can see. I get >>>>>> >>>>>> identical results with and without this option checked. >>>>>> >>>>>> >>>>>> >>>>>> How was this full date option intended to work? >>>>>> >>>>>> >>>>>> >>>>>> /Peter >>>>>> > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > |