implement GEDCOM7 tag DATE:PHRASE#5304
Conversation
* definition of the tag as subtag of events (alas INDI:*:DATE does not work) * checkmark on control panel to show/hide the subtag on edit forms TODO: * rendering on facts & events * translation?
When it contains four digits, these get duplicated. When date itself is absent, there are leading dashes. Maybe move these to .css?
…dcom5 datePhrase `2 DATE (xxx)` Also don't render a hyphen when a date is absent but time is present. Known issue: the new style date phrase will get rendered in the TimeLine chart, but not at other places you might expect it.
…ng rendered as A.D.
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #5304 +/- ##
============================================
- Coverage 35.20% 35.18% -0.03%
- Complexity 11236 11239 +3
============================================
Files 1159 1159
Lines 48108 48142 +34
============================================
Hits 16937 16937
- Misses 31171 31205 +34 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
There is an interesting line in the GEDCOM 5.5.1 specification (page 48), which I hadn't noticed before…
So it would appear that GEDCOM 5.5.1 allows a We should definitely add support for displaying DATE:PHRASE tags, just as we do for other custom tags and GEDCOM 7 tags. But this conflicts with GEDCOM 5.5.1, and webtrees still advertises itself as "100% GEDCOM 5.5.1 compatible". Perhaps we should create |
|
No, this is explicitly GEDCOM7. The tag becomes only available in editing forms when selected in the Control Panel under GEDCOM7 things. If you want/need DATE:NOTE, you know better than I what to do. But that does not allow only a phrase (so without an approximation) |
|
Since the GEDCOM 5.5.1 spec says we can store date phrases in INDI:*:DATE:NOTE, I would probably implement this by adding support for inline notes here, with the label "Date phrase" to indicate that it is has a specific purpose and is not for general notes. Then, if we add DATE:PHRASE, the user will have an edit form with two fields, both labelled as "Date phrase". So, adding the g7 DATE:PHRASE would mean that we also need to remove the g5.5.1 DATE:NOTE. |
fix #5171
I thought I already had a PR for this, but could not find it anymore.