Jun 29, 2009 at 8:51 AM
Edited Jun 29, 2009 at 8:53 AM
I haven't noticed problems with the characters but most of the names in my family don't have special characters so I wouldn't have seen it anyways. I did notice the bug with dates of birth before and it's actually a very strange bug. Currently,
dates are exported in the format dd/mm/yyyy in the GEDCOM file. When you import the dates, family.show tries to parse a date from the dd/mm/yyyy. However for dates of birth it seems it cannot read the dd/mm/yyyy format yet it seems to work OK for
other dates, randomally as you suggest. It could be some confusion with the order of yy/mm. In the US often dates are done mm/dd but the program may get confused between 12/01 and 01/12 which could be 12 Jan or 01 Dec.
The work around I used was to export dates in the format 01 DEC 2009 etc. This solved the issue with dates not being imported for me. Dates were also in this format in other GEDCOM files I had made using other software.
I added this method to GedcomExport.cs:
//converts month number to 3 letter month abbreviation as used in GEDCOM
private string GetMMM(int month)
string monthString = string.Empty;
and whereever there was a date:
string day = date.Value.Day.ToString();
string year = date.Value.Year.ToString();
int month = date.Value.Month;
string monthString =string.Empty;
monthString = GetMMM(month);
string Date = day + " " +monthString+" "+year;
if (date.Value.ToShortDateString() != null)
WriteLine(2, "DATE", Date);
A bit long winded but hope that helps.