* Title template

[BillH]

I'm new to Ancestral Sources and have a question about the title template.

Is there any way to get the name to be in the format 'Last, First' instead of 'First, Last'?  

If not, I'd like to suggest that as a future enhancement.

Thanks!

ID:4733

[nsw]

Not currently but its a good idea and one I'll add to the program today or tomorrow. New version is almost ready to beta test so you won't have too long to wait.

Nick

[nsw]

While you wait for the next version, assuming you're not using the 'Other info' box you could set the template to include the Other field and type in (or copy/paste) the name of the key person into that.

[BillH]

Nick,

Good idea. I'll give that a try. Can't wait to see the new release.

Thanks!

[nsw]

I don't want people to expect too much from the next version. As I've been saying ever since version 1 came out, the next version will be bug fixes, addional features that have been requested and the ability to link images to existing census sources (this is a feature that my previous utility Gedcom Census has but A.S. currently doesn't and will allow me to retire Gedcom Census). The 'other sources' will begin to appear in the subsequent releases.

Best wishes

Nick

[tatewise]

Regarding the Title Template proposal I have the following observations:
KEYPERSON Bug
If a Census Template is modified and a new first column inserted so that the Name column is no longer the first column, then {KEYPERSON} does not work.
Instead [No Name] always appears in the Title even after a person has been added to the census table.
Template Keywords
May I suggest the following Template Keywords:
{KEYPERSON}    Retained for backwards compatibility
{KEYFORENAMES} Key person first names as in GEDCOM file e.g. John Paul
{KEYFORECAPS}  Key person first names in CAPITALS e.g. JOHN PAUL
{KEYINITIALS}  Key person first name initials e.g. J P
{KEYLASTNAME}  Key person last name as in GEDCOM file e.g. McCloy
{KEYLASTCAPS}  Key person last name in CAPITALS e.g. MCLOY
Thus template {KEYLASTCAPS}, {KEYFORENAMES} would mimic Family Historian with last name first in capitals separate with comma from forenames.
e.g. MCCLOY, John Paul

Hope this is not too late for inclusion in next release.

[nsw]

Hi Mike

Yes I implemented something similar to this last night (apart from the initials). There are issues regarding having unwanted comma-space if a surname or first name or both is missing but I don't particularly want to get into a potentially complex set of functions at this stage.

I hadn't spotted that bug before so thanks for reporting, but actually as part of the coding I did to implement the new keywords the error no longer occurs!

Cheers

Nick