Upload a new GEDCOM: can't convert from ANSEL to UTF-8
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
webtrees |
Triaged
|
Wishlist
|
fisharebest |
Bug Description
Steps to reproduce:
go to FamilySearch.org
download a record
in webtrees, go to GEDCOM administration
under Upload a new GEDCOM select a file
a new GEDCOM is created above and shows this error:
Loading data from GEDCOM: 0.0%
Error: cannot convert GEDCOM file from ANSEL encoding to UTF-8 encoding.
Looking at the logs, I do not see any new errors, just a lot of entries where the new GEDCOM is getting setup.
Steps to work around:
run LifeLines, create a new database
u [utilities], R [read from file], select the file downloaded from FamilySearch.org
LifeLines says: Cannot convert codeset (from <ANSEL> to <UTF-8>) Enter codeset to assume (* for none)
enter *
u, s [save to file], enter new filename
repeat the steps to reproduce the bug above, except use the new file
Changed in webtrees: | |
status: | Confirmed → Triaged |
See the ReadMe file, and the WIKI:
http:// wiki.webtrees. net/GEDCOM_ %28family_ tree%29_ FILES
"ANSEL - currently will not import. Gives warning Error: cannot convert GEDCOM file from ANSEL encoding to UTF-8 encoding. Later releases of webtrees may include translation from ANSEL to UTF8, but this is not a simple process."
So yes, a bug of sorts, but a known one (hence the error message), that is not high on the list of To-Do's, so I'll mark this as "wishlist".