Family Historian User Group

Thanks Mike, that's a perfect summation.

"... I am surprised Darrin/TNG disregards that relationship." You tell me, this is the code:- case "_SHAR": $share = new stdClass(); if(preg_match( "/^@(\S+)@/", $lineinfo['rest'], $matches )) { $share->id = $matches[1]; $lineinfo = getLine(); while( $lineinfo['level'] >= $prevlevel + 1 ) { $note = ...

From me to Darrin: ... I thought I read that TNG now supported shared events and I took that to mean witnesses to events. Anyway, on Family Historian I have quite a few of these. For example, My brother and I were witnesses at our mother's death and I have the appropriate witnessed events set up the...

"So we are bemused that Darrin of TNG is suggesting it is the solution Rod was looking for."
And that's being polite.

Thank goodness for your plugin Mike, I'm able to effortlessly remove _SHAR from my gedcom using it.

Thanks Helen, I've just been experimenting with an ASSO import into TNG also. I knew nothing about this tag previously until being straightened out about it here. Everything you say is correct. I ended up with an association on my mother's record like this: Association: Rodney Allan Tilyard (Relatio...

Helen, thanks for weighing in.

I have provided the information here exactly as it was provided to me from TNG.

But it's problematic. Mike isn't updating his plugin anyway.

It appears that way, but Darrin is handling it, not me. I'm just a boring old user, not a software developer. Please have this conversation with him.

Mike, I am not going to rekey the hundreds of witnesses I have in FH. I like the witness support within the product itself. I had the impression from your last post that you were now willing to mod your plugin to accommodate what TNG expects. So be it. Let the problem remain. Instead I will use anot...

Yes, typo thanks Mike, meant ASSO. This is an example gedcom that FH produces: 1 DEAT 2 DATE 23 JAN 2000 2 PLAC Brisbane, Queensland, Australia 2 _SHAR @I496@ 3 ROLE Witness 2 AGE 70y 2 CAUS heat stroke This is what TNG expects: 1 DEAT 2 DATE 23 JAN 2000 2 PLAC Brisbane, Queensland, Australia 2 AGE ...

I wonder why Darrin is disinterested in accommodating the non-standard _SHAR invented by FH? He has stated that FH should be using the industry accepted ASSO and that is what his software supports.

[EDIT: SHAR corrected to ASSO.]

<deep sigh> I give up.

Just want the BUG fixed in FH which is using a _SHAR custom event instead of the ASSO which is what is meant to be used in this case.

Mike, I'm not here to have this debate with you. I've now reported the problem again to FH and awaiting a response.

You've already indicated in an earlier post it was too difficult to change your plugin to output gedcom for witnessed events correctly, as TNG expects.

Mike, it's nothing to do with semantics, or narrative reports (these are fine) and everything to do with FH not producing the correct GEDCOM syntax for witnessed events. As expected, I couldn't find anything in Help which mentions using specific roles for shared events (and which would produce diffe...

Progress, I think Let me look further into how FH uses the role to make the distinction between shared and witnessed events, and importantly, if the correct GEDCOM syntax is used for witness events.

Mike it's simple. I was at my mother's hospital death bed and watched her die. I was a witness to her death. If I was in the same household on census night I would consider that as sharing the event. TNG is correctly managing the difference between a shared event and a witnessed event. There is a di...

Hi Mike, this is from TNG: "When TNG sees _SHAR, it thinks you want to duplicate that event for the people mentioned. If you don't want to do that, then you shouldn't use the _SHAR tag at all. TNG does associations (what most people use for witnesses) with the 1 ASSO tag, as per the GEDCOM standard....

Hi Mike! Hoping you can help me with your 'Export Gedcom File' plugin. Family Historian and TNG have a different interpretation of GEDCOM witnessed events. This is an example from TNG: 1 ASSO @I496 2 TYPE INDI 2 RELA Witness And FH: 2 _SHAR @I496@ 3 ROLE Witness I have corresponded with them and eac...