1.
Make sure that your genealogy program can produce GedCom files with the ANSEL character set. Since ANSEL is the standard character set for GedCom, it should be supported. (see alternative below)

2.
Generate your GedCom file with ANSEL character set.
After generating the GedCom file, open it in wordpad. Check that the following line is present somewhat at the beginning:
1 CHAR ANSEL

3.
Set the parameters in the Joaktree component for
"Conversion to UTF-8". This should take care of your problem.

4.
If your program does not support the generation of ANSEL GedCOm files, choose the option for UTF-8 character set (if present). Check the CHAR line of your GedCOm file, and set your parameter to "No conversion".

5.
If above fails, please, let me know which character set is used in your GedCom file.

Succes

Tnx for the message.

I'm using Aldfaer. I configured Aldfaer to export ANSEL. In the resulting .ged i see " 1 CHAR ANSI". Tryed setting parameters in Joaktree to no conversion, to utf-8 and to unicode. No result.

Tryed setting CHAR to ANSEL manually, with all 3 parameters, still no result.

Beginning of .ged:

0 HEAD
1 SOUR ALDFAER
2 VERS 4.2
2 NAME Aldfaer
1 GEDC
2 VERS 5.5
2 FORM Lineage-Linked
1 CHAR ANSI

Any ideas?

Although ANSI sounds like ANSEL, it is not the same.
I guess that Aldfaer does not support ANSEL fully.

I just downloaded the program and I see that Aldfaer supports the UTF-8 characterset. So, my suggestion is to select the UTF-8 characterset for the generation of your GedCom file.

Then, you should use "no conversion" in Joaktree, since your database should be configured for UTF-8 characterset.

Good luck and let me know if it worked.

Tryed as instructed, still no luck i'm, afraid.

In the persons list not the whole year is visable ( http://www.familiebastiaans.nl/index.php?option=com_joaktree&view=joaktreelist&treeId=1&Itemid=5)

1. Trema problem
I am not sure what is going wrong. I have to perform some test to see whether I can reproduce your issue with Aldfaer. So I have to get back on this one later.

2. Showing year
Apparently all dates end with a space.
The last four characters of a date are shown here, and when the date is "1915 ", the following is shown: "915 ".
I will fix this in release 1.1.1, which will be published within the next week or two.
In the mean time, I do not know why your dates have a trailing space. Perhaps you can remove them yourselve in Aldfaer?

I tried to reproduce the issue with the trema.

I added a fictive person into Aldfaer with last name: Táâãäïèéêëüû

Created a GedCom export with UTF-8 settings and loaded the file into Joaktree (no conversion) and it works fine.

GedCom looks like following example
==
0 HEAD
1 SOUR ALDFAER
2 VERS 4.2
2 NAME Aldfaer
2 CORP Stichting Aldfaer
1 SUBM Unknown
1 GEDC
2 VERS 5.5
2 FORM Lineage-Linked
1 CHAR UTF-8
0 @I1@ INDI
1 RIN 1
1 NAME Niels /Táâãäïèéêëüû/
1 SEX M
1 FAMS @F1@
1 _NEW
2 TYPE 1
2 DATE 25 JAN 2010
3 TIME 21:49:44
0 TRLR