Open changeling opened 4 years ago
Just created a new milestone 3.0.0 (maybe 4.0.0) for this. It's something I thought about for a long while.
Since I overtook the whole project I wanted to review the 5.5.1
specification and compare it to the current functionality of the parser anyway. Maybe there can be something optimized and added.
After that it may be a good time to think about full 5.5.5
support, compatibility and the automatic detection if the input or file is a 5.5.1
or 5.5.5
specified file. This should lead to better differentiations between different kind of functionality within the parser.
This will need time but is something to be kept in my mind :)
Thank you for your request!
You bet! Thank you for all your efforts.
You might take a look at Nigel Munro Parker's ged-inline code at (https://github.com/nigel-parker/gedinline). He has some great grammar/tag validation stuff there, in src/main/docs/,
src/main/resources/, and
src/main/java/gedinline/...`
Might be some short cuts for ya there. If I have time, I'll try to join in here, but right now I'm kinda swamped.
New GEDCOM tags are coming with this PR: https://github.com/nickreynke/python-gedcom/pull/49
Thanks for the heads-up! So great to see!
Is your feature request related to a problem? Please describe. 5.5.1 has become the most common standard for usage. That said, Tamura Jones 5.5.5, which is fully 5.5.1-backwards compatible is likely to supplant this going forward. It would be great to see 5.5.1/5.5.5 parsing implemented. I can't seem to find discussion of this in the docs, so posting this as part query (Do you plan to...) and part request (Man, it would great if...).
Describe the solution you'd like See above.
Additional context https://www.gedcom.org/gedcom.html