Solved Error: converting GEDCOM files from UNICODE

Hi,

I'm using PGV on other hosting. Now decided to move to my own familyname.name
PGV is installed under familyname.name/family
I'm trying to convert to webtrees and got error below:

0% Error: converting GEDCOM files from UNICODE encoding to UTF-8 encoding not currently supported.

What do I do wrong?

Thanks,
Ivan

There is no such thing as "UNICODE encoding". It is a general term that covers many different actual encodings. The most common is "UTF-8", with "UTF-16LE" and "UTF-16BE" used occaisionally.

So, your GEDCOM file contains a header saying "This file is encoded in UNICODE", and webtrees doesn't know what that means.

I've created an online tool that should be able to fix this. It looks at the actual data, and works out which of the common encodings is actually used, converts to UTF-8 and updates the headers.

dev.webtrees.net/ansel/

FYI, this tool does not keep any copy of your data.

It was UTF8, I just change CHAR UNICODE to CHAR UTF8 in ged file. It's accepting now the file itself.
But conversion from PGV doesn't passed properly.

I've checked settings on my PGV installation. Option "Use the database to provide UTF-8 collation" if off and I have all Russian names displayed properly. But it shown wrong charset if I change this option to On.
Also for some reason most of the tables in MySQL database has got latin1_swedish_ci collation and some of them utf8_general_ci.
Is there any solution to properly transcode properly all names and places?

Also I've tried to convert collations inside of the MySQL database with ALTER TABLE pgv_news CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;
but it still shows incorrect.

Search the forum for conversion options. There is a utility for this that Greg wrote. Special character encoding was often an issue with PGV data files.

Looks like it's all related only to usernames ans news, which I can fix. All names from ged file were converted properly.

Problem solved.