Question
Date localisation
- Franz Frese
-
- Offline
- Platinum Member
-
Less
More
2 weeks 5 days ago #116908
by Franz Frese
If genealogical work isn't meant to be shared, I wonder what it's meant to be at all: For to get help, tell the address of your webtrees site!
mine is: freris.de
Replied by Franz Frese on topic Date localisation
There is nothing " between January and February 1900"
If genealogical work isn't meant to be shared, I wonder what it's meant to be at all: For to get help, tell the address of your webtrees site!
mine is: freris.de
Please Log in or Create an account to join the conversation.
- TheDutchJewel
-
- Offline
- Junior Member
-
2 weeks 5 days ago - 2 weeks 5 days ago #116909
by TheDutchJewel
I've changed it to: "between January and March 1900".
• webtrees 2.0.19 (last 2.0.x version that Vesta fixed for changed markdown implementation)
+ Laragon 8.6.1 with PHP 7.4.33 + Rural & Primer theme + Vesta & other modules
• latest webtrees 2.2.x (only for testing and presentation) + PHP 8.5.x
Replied by TheDutchJewel on topic Date localisation
That's right, that was a wrong example.There is nothing " between January and February 1900"
I've changed it to: "between January and March 1900".
• webtrees 2.0.19 (last 2.0.x version that Vesta fixed for changed markdown implementation)
+ Laragon 8.6.1 with PHP 7.4.33 + Rural & Primer theme + Vesta & other modules
• latest webtrees 2.2.x (only for testing and presentation) + PHP 8.5.x
Last edit: 2 weeks 5 days ago by TheDutchJewel.
Please Log in or Create an account to join the conversation.
- hermann
-
- Offline
- Elite Member
-
2 weeks 4 days ago #116912
by hermann
That is not correct. BET JAN 1900 AND FEB 1900 is any day between 1st of January and the last day in February 1900. The borders are inclusive in GEDCOM 5.5.1 and 7.
5.5.1: Event happened some time between date 1 AND date 2. For example, bet 1904 and 1915 indicates that the event state (perhaps a single day) existed somewhere between 1904 and 1915.
7: BET x · Exact date unknown, but no earlier than x. AND x · Exact date unknown, but no later than x.
Hermann
Designer of the custom module "Extended Family"
webtrees 2.2.6 (100 custom modules installed, PHP 8.4.10, MariaDB 10.6) @ ahnen.hartenthaler.eu
Replied by hermann on topic Date localisation
There is nothing " between January and February 1900"
That is not correct. BET JAN 1900 AND FEB 1900 is any day between 1st of January and the last day in February 1900. The borders are inclusive in GEDCOM 5.5.1 and 7.
5.5.1: Event happened some time between date 1 AND date 2. For example, bet 1904 and 1915 indicates that the event state (perhaps a single day) existed somewhere between 1904 and 1915.
7: BET x · Exact date unknown, but no earlier than x. AND x · Exact date unknown, but no later than x.
Hermann
Designer of the custom module "Extended Family"
webtrees 2.2.6 (100 custom modules installed, PHP 8.4.10, MariaDB 10.6) @ ahnen.hartenthaler.eu
Please Log in or Create an account to join the conversation.
- TheDutchJewel
-
- Offline
- Junior Member
-
2 weeks 4 days ago #116913
by TheDutchJewel
You're right, too. According to the GEDCOM specification, it is indeed correct, because BET ... AND ... means "not earlier than" the first date and "not later than" the second.
In ordinary language, however, "between A and B" is often interpreted as excluding A and B themselves. Therefore, a phrase such as "between January and February 1900" may feel wrong or confusing to readers, even though it is technically correct according to GEDCOM.
• webtrees 2.0.19 (last 2.0.x version that Vesta fixed for changed markdown implementation)
+ Laragon 8.6.1 with PHP 7.4.33 + Rural & Primer theme + Vesta & other modules
• latest webtrees 2.2.x (only for testing and presentation) + PHP 8.5.x
Replied by TheDutchJewel on topic Date localisation
That is not correct. BET JAN 1900 AND FEB 1900 is any day between 1st of January and the last day in February 1900. The borders are inclusive in GEDCOM 5.5.1 and 7.
5.5.1: Event happened some time between date 1 AND date 2. For example, bet 1904 and 1915 indicates that the event state (perhaps a single day) existed somewhere between 1904 and 1915.
7: BET x · Exact date unknown, but no earlier than x. AND x · Exact date unknown, but no later than x.
You're right, too. According to the GEDCOM specification, it is indeed correct, because BET ... AND ... means "not earlier than" the first date and "not later than" the second.
In ordinary language, however, "between A and B" is often interpreted as excluding A and B themselves. Therefore, a phrase such as "between January and February 1900" may feel wrong or confusing to readers, even though it is technically correct according to GEDCOM.
• webtrees 2.0.19 (last 2.0.x version that Vesta fixed for changed markdown implementation)
+ Laragon 8.6.1 with PHP 7.4.33 + Rural & Primer theme + Vesta & other modules
• latest webtrees 2.2.x (only for testing and presentation) + PHP 8.5.x
Please Log in or Create an account to join the conversation.
- hermann
-
- Offline
- Elite Member
-
2 weeks 22 hours ago - 2 weeks 22 hours ago #116931
by hermann
Hermann
Designer of the custom module "Extended Family"
webtrees 2.2.6 (100 custom modules installed, PHP 8.4.10, MariaDB 10.6) @ ahnen.hartenthaler.eu
Replied by hermann on topic Date localisation
There is an old issue regarding date and German: FROM is translated as "von". That is normally correct (regarding a location/place), but not with date: "FROM 1850" has to be "ab 1850" and not as now "von 1850".
Hermann
Designer of the custom module "Extended Family"
webtrees 2.2.6 (100 custom modules installed, PHP 8.4.10, MariaDB 10.6) @ ahnen.hartenthaler.eu
Last edit: 2 weeks 22 hours ago by hermann.
Please Log in or Create an account to join the conversation.
- Franz Frese
-
- Offline
- Platinum Member
-
2 weeks 14 hours ago #116932
by Franz Frese
If genealogical work isn't meant to be shared, I wonder what it's meant to be at all: For to get help, tell the address of your webtrees site!
mine is: freris.de
Replied by Franz Frese on topic Date localisation
Man könnte ja auch "Seit 1850" verwenden.
If genealogical work isn't meant to be shared, I wonder what it's meant to be at all: For to get help, tell the address of your webtrees site!
mine is: freris.de
Please Log in or Create an account to join the conversation.
- fisharebest
-
Topic Author
- Offline
- Administrator
-
2 weeks 4 hours ago #116933
by fisharebest
github.com/fisharebest/webtrees/blob/mai...s/German.php#L43-L44
If this is wrong, create a PR/Issue.
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Replied by fisharebest on topic Date localisation
This can be fixed easily. Dates have their own translations. I used the existing translations, and filled in gaps using online translation tools.There is an old issue regarding date and German: FROM is translated as "von". That is normally correct (regarding a location/place), but not with date: "FROM 1850" has to be "ab 1850" and not as now "von 1850".
github.com/fisharebest/webtrees/blob/mai...s/German.php#L43-L44
If this is wrong, create a PR/Issue.
Greg Roach - greg@subaqua.co.uk - @fisharebest@phpc.social - fisharebest.webtrees.net
Please Log in or Create an account to join the conversation.
- bertkoor
-
- Offline
- Platinum Member
-
- Greetings from Utrecht, Holland
2 weeks 2 hours ago - 2 weeks 2 hours ago #116934
by bertkoor
stamboom.BertKoor.nl runs on webtrees v2.2.6
Replied by bertkoor on topic Date localisation
It's a pity that we have not yet gotten any (explicit) comments from users of other languages which use non-latin scripts. If your keyboard is eg Cyrillic, then I have no idea how Latin letters are typed. These people seem to manage, but it must be slow, having to switch etc.
Date entry strongly resembles raw GEDCOM. I'd rather not see that change (it is fast to type) but an isolation between storage and presentation is needed.
Translation of dates in both directions would be great. You need to serve both novices and advanced users.
A year ago or so I did an investigation what should be done to introduce another (the Chinese) calendar. Never got around to reporting my findings...
From the top of my head (and ignoring the fact that GEDCOM representation and date conversion for the Chinese calendar are not trivial) :
I probably forgot some.
Date entry strongly resembles raw GEDCOM. I'd rather not see that change (it is fast to type) but an isolation between storage and presentation is needed.
Translation of dates in both directions would be great. You need to serve both novices and advanced users.
A year ago or so I did an investigation what should be done to introduce another (the Chinese) calendar. Never got around to reporting my findings...
From the top of my head (and ignoring the fact that GEDCOM representation and date conversion for the Chinese calendar are not trivial) :
- The javascript date picker cannot handle other calendars than Gregorian. If I were testing a calendar which is alien to me, I do need that date picker.
- Enumerations of calendar names and month literals are scattered around in webtrees core php code, a separate php library and also javascript code.
- If showing raw (English) GEDCOM data can be prevented, that would benefit a significant group of users. However webtrees should still accept it. Maybe the text entry field should be accompanied with text field(s) showing the resulting raw gedcom and translated version?
I probably forgot some.
stamboom.BertKoor.nl runs on webtrees v2.2.6
Last edit: 2 weeks 2 hours ago by bertkoor.
Please Log in or Create an account to join the conversation.
- Sir Peter
-
- Offline
- Premium Member
-
Less
More
- Posts: 536
1 week 6 days ago #116936
by Sir Peter
Peter
Replied by Sir Peter on topic Date localisation
I‘d say the difference here between from (German „ab“) and since (German: „seit“) is that at least in English since („seit“) is more strictly referring to an ongoing process or a status still valid today. I‘d prefer the German „ab“.Man könnte ja auch "Seit 1850" verwenden.
Peter
Please Log in or Create an account to join the conversation.