Thank everyone UTF-8 works fine
On Wed, 23 Jan 2019 at 12:24, Beryl & Mike Tate <post(a)tatewise.co.uk> wrote:
To cope with the extended character set for foreign accented letters, etc,
FH V6 now uses Unicode UTF-16 format for the GEDCOM file.
Unfortunately, many products such as Ancestry do not recognise that
character encoding format.
You can change that in FH using Tools > Preferences > File Load/Save to
use UTF-8 format.
OR you can use the File > Import/Export > Export > GEDCOM File command and
choose UTF-8 format.
BUT the GEDCOM file will still probably contain some data that Ancestry
will not recognise, because FH V6 has added so many features
not in FH V2.
e.g. Place records and Fact Witnesses.
So, I advise that you use the 'Export Gedcom File' Plugin with the (ANC)
Ancestry option that produces an Ancestry compatible GEDCOM
Regards, Mike Tate
You cannot add screenshots to these Plain Text FHU Emails.
But you can add them to the FHUG Forums, where there is more advice about
From: Sheila Beer <sheilamarcelb(a)gmail.com>
Sent: 23 January 2019 10:58
To: Family Historian <family-historian-users(a)rootsweb.com>
Subject: [FHU] uploading a GEDCOM to Ancestry
I am trying to upload to Ancestry.
I had no problem when I was using version 2 but since Dec 2018 I am now
using version 6 Family Historian but I get this message:- Error: The file
you have specified (Sheila relatives only 23 Jan 2019.ged) does not appear
to be a valid GEDCOM file, please try again.
The file was created using version 6.
My file tells me it is a GEDCOM file - see enclosed screenshot, so why
will Ancestry not accept the file.
ps I use windows 10
Email preferences: http://bit.ly/rootswebpref
Privacy Statement: https://ancstry.me/2JWBOdY
Terms and Conditions:
Rootsweb Blog: http://rootsweb.blog
RootsWeb is funded and supported by Ancestry.com
and our loyal RootsWeb