Round 2: Using RootsMagic 188.8.131.52 this time:
- The TMG [s] variable refers to the witness when it appears in a witness sentence. Example TMG witness sentence: “[s] was cited as the nearest relative of [P1] on his military registration <[D]><[L]><. [WM]>” translates in RM to: “[Person] was cited as the nearest relative of [Person] on his military registration <[Date]><[Place]><. [WM]>”
[s] should have been translated to [ThisPerson] if it was a witness sentence, [Person] if the principal's sentence and that is what I have observed. [WM] does not translate so it is left as a flag for you to fix.
- <[L]> should be translated to <[PlacesDetails]><[Place]>. This would fix several sentences in my import. If [PlaceDetails] is blank, there is no harm done. If it has something in it, the TMG [L] variable always includes those values.
Agreed, except it should be < [PlacesDetails]>< [Place]>. RootsMagic does not auto-space variables so it is necessary to account for them in the sentence template. That's what is done by my interim patch TMG-RM Fact Sentence Tweaks.
- My TMG birth tags have no witnesses cited. It appears the import adds Parent witnesses whether they appeared in TMG or not:
Strange. I have not seen unintended shared Birth events in direct imports of the TMG Sample database nor of a 5000 person project.
- An RM Parent witness was created for the mother with the sentence: “[Husband] was born a [PAR] on <[Date]><[Place]><. [Desc]>”. This is almost a translation of the default TMG parent witness sentence, but it puts no spaces between the date and place as the TMG variables do and neither the parent, nor the child was a "husband".
Strange again. Is this an extension of the previous problem? Was this a custom Birth tag with two principals? Is P1 the mother? Again, no auto-spacing for variables - must be explicit - interim patch TMG-RM Fact Sentence Tweaks also spaces <[Date]>.
- An RM Parent witness was created for the father with exactly the same sentence generated for the mother. In neither case (mother or father) does RM recognize [Husband] as a translatable variable.
If it is a single-principal event, [Husband], [Wife], [Spouse], [Couple] have no meaning. But we're still back to why your Birth events have these supposedly auto-generated Father/Mother witnesses and what I have seen does not.
- A TMG Misc. tag has the customized witness sentence: “[W] was an attendee when [P1] was a presenter at the Mid-south Training for Service <[D]> <[L]>”. This was imported to the RM witness sentence: [ThisPerson] was an attendee when [Husband] was a presenter at the Mid-south Training for Service <[Date]> <[Place]>.” The witness was a female not even related to the principal who was also female and certainly not her “wife.”
This sounds like a 2-Principal tag in TMG being converted to an individaul fact type in RM. The nearest equivalent to [P1] is [Husband] and to [P2] is [Wife]. Consider those to be just names of variables and not indicative of gender. However, they do point to fields of the same name in FamilyTable. If detected as an individual fact type, then [P1] should translate to [Person]. If there is no immediate fix, I think a SQLite query could be devised to hunt these out and change them.
- People who have used two Principals in TMG for events other than family events (marriage, census, etc) are going to run into problems that are unavoidable. Thus the translation of [P] or [P1] should be [Person] in almost every case. [Spouse] might be used for [P2] or [PO] in family events, but I would think [Husband] would have very limited application for the purposes of this import.
Witness role of Best Man: [This Person] was [Husband:casual:poss] best man...
Witness role of Bridesmaid: [This Person] was [Wife:casual:poss] bridesmaid...
- It appears that as a rule, the TMG [M] variable is translated to [Desc] or [Desc:A] but then the TMG memo value is copied to the RM Notes field and the description field is left blank. Since there is no RM memo variable, could the memo value also be copied to the description so the RM sentences would be closer to functional?
Yes. TMG 9.04 GEDCOM does. And direct import does for a few fact types, e.g., Education, Occupation. For an interim fix, see Events - Move Short Note to Description
- TMG graduation sentence: “[P] <was|and [PO] were> graduated <[D]> from < [L]> <[M]>”. This was translated in RM to “[Person] attended < [Place]><[Date]><. [Desc]>.” The import moved the TMG Addressee field to Place Details and then the sentence omits [PlaceDetails]. And again the TMG memo was moved to Notes and then the sentence refers to [Desc].
Presumably the standard TMG Graduation fact mapped to the standard RM Graduation fact so you get the standard RM sentence? And because it is an individual fact type, [PO] cannot be translated. That said, were it a family fact, <was|and [PO] were> are often carried over but does not function correctly under RM rules; it needs to be changed to <and [Spouse] were|was> as done in TMG-RM Fact Sentence Tweaks.
Unfortunately for me, it looks like almost all but the most straightforward TMG events will require a significant amount of reworking due to issues like the ones cited above. These were found reviewing the events in just one family. I certainly understand that this import is a complex problem. I hope these comments are constructive.