-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GeneaProve could not import your file: None #20
Comments
"None" is supposed to be the error message reported by the importer, but obviously it is not especially
Let me know whether this gives more information regards |
Thanks Emmanuel for your reaction.
Removed the offending line.
Reformatted the lines to be shorter than 255 characters.
Removed the SUBM tagged line which referenced @sub1@
Now I'm stuck on the concatenation error. |
Hello, I am finally getting back to geneaprove a bit. I am not able to fix the issues you reported since I have lifted the restriction on the long lines, which most likely was the most painful issue in I have also validated the _UID tag under FAM (geneaprove is intentionally overly restrictive Please let me know if you are still interested in investigating geneaprove, and if it is possible thanks |
Hi Emmanuel, Thanks for responding. Kindly, oriste
|
Hi, I'm trying to import a gedcom file that has been generated by Reunion on OS X. There were many tags not recognised which I removed. Finally all tags left passed and I got the following message:
"GeneaProve could not import your file. This is either because your file does not contain correct GEDCOM data, or more likely because of limitations in GeneaProve. Please Report this issue to the GeneaProve developers. If your GEDCOM data contains information you wish to keep private, you can use the script gedcom_anon.py to anonymize the data before you send it to us.
None"
It is the "None" in the last line that puzzles me. Any idea where I should look to correct my input file myself, before I anonymise and send it to you? I am aware that you are not supporting Reunion, but I can live with that for now.
Thanks.
The text was updated successfully, but these errors were encountered: