I'm tweaking the report defined by cemeterylist.xml to list married names. Seems sensible as most gals aren't buried under their maiden names.
Minor problem is that `<PGVRGedcomValue tag:"NAME:_MARNM">` returns the slashes around the surname where as `<PGVRGetPersonName>` doesn't. This outputs:
Frank Browning
Lilly /Browning/
Any suggestions or should I raise a RFE?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-10-13
I think it would have to be an RFE.
But, which married name do you want it to use? I have plenty of women with two or three or them. Presumably the most recent one, so you would need to do a check on various marriage dates first, assuming they exist.
What about cases (not so unusual) where a divorced woman reverts to using her maiden name? I can't think of a way to capture that one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
PGVRGedcomValue handles unmodified plain text only. The slashes can be useful as they gives a visual aid about the married name part?
Personally, I would print all the married names, if any, to have a complete overview, as kiwi pointed out a couple of problems, by changing PGVRGedcomValue to:
When you folks get it sorted out, would you explain it to me in plain English, as I have been looking for a "married name" option for death and/or cemetery reports.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm looking for clarification also. For a cemetery report, wouldn't you want the name on the stone, whether it was maiden name, married name, secret identity or whatever?
Since PGV probably can't see the stone, next choice might be all names.
??
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As kiwi pointed out, it's virtually impossible to calculate the correct married name. If this would be simple, then I guess a developer would already made a function to cover this.
So, the best thing is to print all married names, if exist, like with the Lists => Individuals
If the name on the stone is neither, by any reason, you still have the chance to make a note with the correct name, example:
1 BURI
2 NOTE Name on the headstone: Jane Doe-2nd Marnm
I have uploaded a Death …. report. This one has a drop-down list instead. I thought, I try something new, more user options. Which one is better? The cemetery or the Death report?
Imsza: Hmmm, the jury's still out on that, but I'm leaning slightly to the Cemetery style check-box. I'm inclined to think the "M:" is just a distraction, as it's obvious that these are the correlated married names.
Might need to play with it a bit, so let's get a few more votes.
Thanks again for your contributions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The 'M: ' and 'H: ' is distracting for me too. It takes 2 sec and it's gone. (this is just a test)
I'm also for the drop-down list as it gives me more options, the husbands, specifically when married names are missing. Not to mention, special headstone text like "Here lies John Smith and wife" :)
So much for the married names. There is no law of what a headstone text can or has to say. So, with a Husband option, I give me self a better chance. And usually, I don't use married names, for I don't know all of them but I do have the names of the husbands.
With the drop-down box (the 3 options), might be more user who will 'enjoy' the reports for being more 'flexible'. But this is just me. Any other vote?
Your welcome,
-Im
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tried the URL but not sure if that is where I should find the dowload file. Do i just add it to where the original file is in PGV? Married names, if known, are great help.
I currently use my offline app for report to add other options not in PGV report. This is one.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Kerry
"I suppose the next thing I need is a report…..females"
Not sure what you mean, but ADMIN > BATCH > ADD MISSING MARRIED NAMES already exists. Many thanks to Greg.
-Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mac:
Make a backup of those 2 files, in case you don't like them. Yes, just over write those files. Yes, those are the 2 files where the link takes you. If something is missing from any report, you can always add it or make your own to suit your purpose, there is no need for any other apps…
Kerry: I have something like that :)
-Im
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm tweaking the report defined by cemeterylist.xml to list married names. Seems sensible as most gals aren't buried under their maiden names.
Minor problem is that `<PGVRGedcomValue tag:"NAME:_MARNM">` returns the slashes around the surname where as `<PGVRGetPersonName>` doesn't. This outputs:
Frank Browning
Lilly /Browning/
Any suggestions or should I raise a RFE?
I think it would have to be an RFE.
But, which married name do you want it to use? I have plenty of women with two or three or them. Presumably the most recent one, so you would need to do a check on various marriage dates first, assuming they exist.
What about cases (not so unusual) where a divorced woman reverts to using her maiden name? I can't think of a way to capture that one.
PGVRGedcomValue handles unmodified plain text only. The slashes can be useful as they gives a visual aid about the married name part?
Personally, I would print all the married names, if any, to have a complete overview, as kiwi pointed out a couple of problems, by changing PGVRGedcomValue to:
<PGVRRepeatTag tag="NAME:_MARNM">
<br /><PGVRGedcomValue tag="_MARNM" />
</PGVRRepeatTag>
When you folks get it sorted out, would you explain it to me in plain English, as I have been looking for a "married name" option for death and/or cemetery reports.
I'm looking for clarification also. For a cemetery report, wouldn't you want the name on the stone, whether it was maiden name, married name, secret identity or whatever?
Since PGV probably can't see the stone, next choice might be all names.
??
Clarification…
As kiwi pointed out, it's virtually impossible to calculate the correct married name. If this would be simple, then I guess a developer would already made a function to cover this.
So, the best thing is to print all married names, if exist, like with the Lists => Individuals
If the name on the stone is neither, by any reason, you still have the chance to make a note with the correct name, example:
1 BURI
2 NOTE Name on the headstone: Jane Doe-2nd Marnm
: https://sourceforge.net/tracker/?func=detail&aid=2880048&group_id=55456&atid=477081
Did anyone tested the report I have uploaded? Is that ok?
Or would it be better to print the husbands name? Or maybe one or the other depending a drop-down select list?
Imeza: That is great, and thank you. Can we get the same thing for a "Death Date & Place Report" or deathlist.xml?
I have uploaded a Death …. report. This one has a drop-down list instead. I thought, I try something new, more user options. Which one is better? The cemetery or the Death report?
Which one should be the same as the other?
-Im
: https://sourceforge.net/tracker/?func=detail&aid=2880048&group_id=55456&atid=477081
Imsza: Hmmm, the jury's still out on that, but I'm leaning slightly to the Cemetery style check-box. I'm inclined to think the "M:" is just a distraction, as it's obvious that these are the correlated married names.
Might need to play with it a bit, so let's get a few more votes.
Thanks again for your contributions.
Thanks for your vote.
The 'M: ' and 'H: ' is distracting for me too. It takes 2 sec and it's gone. (this is just a test)
I'm also for the drop-down list as it gives me more options, the husbands, specifically when married names are missing. Not to mention, special headstone text like "Here lies John Smith and wife" :)
So much for the married names. There is no law of what a headstone text can or has to say. So, with a Husband option, I give me self a better chance. And usually, I don't use married names, for I don't know all of them but I do have the names of the husbands.
With the drop-down box (the 3 options), might be more user who will 'enjoy' the reports for being more 'flexible'. But this is just me. Any other vote?
Your welcome,
-Im
Tried the URL but not sure if that is where I should find the dowload file. Do i just add it to where the original file is in PGV? Married names, if known, are great help.
I currently use my offline app for report to add other options not in PGV report. This is one.
I suppose the next thing I need is a report to look for all dead married females where I don't have _NMARN set. ;-)
Kerry
"I suppose the next thing I need is a report…..females"
Not sure what you mean, but ADMIN > BATCH > ADD MISSING MARRIED NAMES already exists. Many thanks to Greg.
-Stephen
Mac:
Make a backup of those 2 files, in case you don't like them. Yes, just over write those files. Yes, those are the 2 files where the link takes you. If something is missing from any report, you can always add it or make your own to suit your purpose, there is no need for any other apps…
Kerry: I have something like that :)
-Im
Also the address labels should be printed with the current (married) name.
Meliza