Re: [Gramps-devel] fixing age calculation in report utils

[Douglas S. B. <db...@cs...>]

> HI -- there is a FIXME in _ReportUtils that I'm looking at.
> Specifically, it suggests replacing some in-line code with a call to
> estimate_age. I started to look at it and put together some code, then
> I got to wondering:
>
> 1. The current in-line code can report age in years, months or days
> but estimate_age can only do it in years.  How serious is losing
> months and days?  Note that the current code doesn't work properly for
> all calendars.

It depends. In some places it is useful, and I've added support in
gen/lib/date.py to support it.

> 2. Can I have a birthdate in one calendar (say Hebrew) and a death
> date in another (say Julian) calendar?

Yes, in the Date class you can.

> 3. If the answer to 2 is "yes", does estimate_age still work correctly?

I don't know, but if you want to test and report back I'd be glad to help
make a better estimate age.

BTW, I'm think of two modes for estimate ages:

1) a quick-n-dirty version (like the current one)

2) a thorough, deep-search that will go to all possible lengths to find an
age.

-Doug

> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Gramps-devel mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>