Please do NOT expect all Feature Requests to be actioned automatically. Describing your proposal here will ensure the development team are aware of it, and they will give it careful consideration.
  • Page:
  • 1

TOPIC:

Readability of calendar conversions 1 week 1 day ago #1

  • WGroleau
  • WGroleau's Avatar Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
  • Posts: 2051
If I put
2 DATE HEBREW 5130
it gets displayed as
5130 (1370)
which is going to be confusing to visitors and uninitiated members. Might be better as
5130 (Hebrew calendar—1370 C.E.)
Maybe there could be an admin option to chose "C.E." or "A.D."

Also, for genealogy, B.C. or B.C.E. might not be useful, but what about history?
2 DATE HEBREW 3000
is currently rendered
3000 (-761)

I started an experiment with biblical genealogies¹ Since the Hebrew calendar purports to show years from creation, I put the birth of Seth as
2 DATE HEBREW 130
which is displayed as merely
130
What should be done with that, if anything?

¹The issue is how these dates should be displayed. Whether the bible is history or myth is an hot-button to many but should not be argued here..
--
Wes Groleau
UniGen.us/

Please Log in or Create an account to join the conversation.

Last edit: by WGroleau.

Readability of calendar conversions 1 week 19 hours ago #2

  • hermann
  • hermann's Avatar
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 829
You say that you entered
2 DATE HEBREW 5130
but it should be
2 DATE @#DHEBREW@ 5130

You are right that the display "5130 (1370)" is not intuitiv. There should be a bit more information shown.

If you enter
2 DATE FROM @#DHEBREW@ 3760 TO @#DJULIAN@ 1 B.C.
that is shown as
from 3760 (-1) to 1 BC (-1)
i.e 3760 (hebrew) = 1 BC (Julian) = -1 (Gregorian ???)
Hermann
Designer of the custom module "Extended Family"

webtrees 2.1.16 (all custom modules installed, PHP 8.2, MySQL 5.7) @ ahnen.hartenthaler.eu

Please Log in or Create an account to join the conversation.

Readability of calendar conversions 1 week 19 hours ago #3

  • WGroleau
  • WGroleau's Avatar Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
  • Posts: 2051

You say that you entered
2 DATE HEBREW 5130
but it should be
2 DATE @#DHEBREW@ 5130

Ah, I thought I had seen a different syntax but didn't remember what it was. So I used the syntax in the GEDCOM 7 spec. I would add to my suggestion that webtrees support both input formats as well as improve the display format. And don't forget the discontinuity (the lack of a year zero) in the conversion functions.
--
Wes Groleau
UniGen.us/

Please Log in or Create an account to join the conversation.

Last edit: by WGroleau.

Readability of calendar conversions 1 week 18 hours ago #4

  • hermann
  • hermann's Avatar
  • Offline
  • Premium Member
  • Premium Member
  • Posts: 829
You can see the GEDCOM 5.5.1 format when entering a date in webtrees by using the help icon = "?".

You are right, webtrees is already supporting the GEDCOM 7 format using "HEBREW" instead of "@#DHEBREW@" in 5.5.1. There is another change: GEDCOM 5.5.1 is using "B.C.", GEDCOM 7 is using now "BCE". Another miracle: GEDCOM 5.5.1 allows B.C. for the Hebrew calendar. I don't know what the meaning is of that.

Yes, it is nice that webtrees supports already now the GEDCOM 7 keywords for the calendar system. In GEDCOM 7 the "custom" webtrees calendars "Islamic" and "Jalali" should start with an "_" to indicate that they are custom calendar systems.

One minor remark about conversion from the hebrew calendar to the gregorian calendar: this is not exact because of the start of day at sunset or midnight in those calendars.

And yes: the important point in your post is: "present the information in a way that is understandable and clear".
Hermann
Designer of the custom module "Extended Family"

webtrees 2.1.16 (all custom modules installed, PHP 8.2, MySQL 5.7) @ ahnen.hartenthaler.eu

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Powered by Kunena Forum