* Custom citation template question...

[fhtess65]

Ok - I played around today with creating my own citation template. Mostly it worked, however, I can't figure out what the punctuation parameters are. At the end of some fields, FH places a period, while at the end of others, a semi-colon. Is there any way for me to define what FH does?

I've uploaded two screencaps. One is my template, while the other is the finished citation. I want to be able to put a colon after the word citing, but FH has insisted on a semi-colon.

Any hints?

Thanks...I have to admit, overall, I'm very impressed with the template builder.

Teresa

ETA: I have already amended a little as I noticed some errors, however, I still can't figure out that punctuation.

[ColeValleyGirl]

Does putting a colon after register details in the footnote definition not work? I'm away from my PC at the moment, so can't try it.

[dhwalt]

There are lots of variations that you can build into a custom template to better handle text, punctuation, missing data items...
Below a simple first step, which I have not tried, as a starting point:

{Type}. {Country}. {Place}. {Date}. {Name}; {register_details}; <citing: {Original_source}>. {Collection}. {Online_Repository}. <acc: {access_date}>

Example <...> and missing Original_Source data then citing: will not print. The enclosing <> can include one or more terms.

[fhtess65]

Thank you so much for the tip! I've little experience working with these templates, so now I know to enclose in sideways brackets, I can work on it.

Really appreciate the tip

Teresa

There are lots of variations that you can build into a custom template to better handle text, punctuation, missing data items...
Below a simple first step, which I have not tried, as a starting point:

{Type}. {Country}. {Place}. {Date}. {Name}; {register_details}; <citing: {Original_source}>. {Collection}. {Online_Repository}. <acc: {access_date}>

Example <...> and missing Original_Source data then citing: will not print. The enclosing <> can include one or more terms.

[fhtess65]

Thanks, Helen. I did try that and it didn't work. The solution below, however, did.

Now I have one template down, I can clone and create all the others I need

Really appreciate all the help I get here in this forum.

I did, however, have one more question. I prefer my dates to be 02 Feb 1806, yet I FH automatically expands the month to its full version. I can't seem to find anywhere in the preferences to reset that. Is this possible? If not, it's not a huge deal breaker.

Thanks again!

Teresa

Does putting a colon after register details in the footnote definition not work? I'm away from my PC at the moment, so can't try it.

[fhtess65]

That definitely worked!!! Thank you sooo much!!

Teresa

There are lots of variations that you can build into a custom template to better handle text, punctuation, missing data items...
Below a simple first step, which I have not tried, as a starting point:

{Type}. {Country}. {Place}. {Date}. {Name}; {register_details}; <citing: {Original_source}>. {Collection}. {Online_Repository}. <acc: {access_date}>

Example <...> and missing Original_Source data then citing: will not print. The enclosing <> can include one or more terms.

[dhwalt]

When you develop these custom templates then you may find mystery blanks spaces appearing. A tip for 2021 enclose the statement with <> to suppress blank space creation i.e.

<{Type}. {Country}. {Place}. {Date}. {Name}; {register_details}; <citing: {Original_source}>. {Collection}. {Online_Repository}. <acc: {access_date}>>

[fhtess65]

Thanks for the additional info! I really appreciate your help

Teresa

[dhwalt]

Teresa,
"...I did, however, have one more question. I prefer my dates to be 02 Feb 1806, yet I FH automatically expands the month to its full version. I can't seem to find anywhere in the preferences to reset that. Is this possible? If not, it's not a huge deal breaker..."

Your dates will have Type - Date which will auto expand as you note above. Convenient for date entry and it can be changed but in a basic manner and with downsides. In the Source Template Definition (Custom/Editable) window double click on your date field and the Source Template Field Definition dialogue will open. Change Type to Text and OK to close then Save. You then have your date in whatever format you want as text BUT lose auto expand i.e. qualifiers like {Your_Date:YEAR} etc etc. You would also have to re-enter all dates wherever the template has been used.

Help > Source Template Formats is a good place to start.

[fhtess65]

Thanks That makes sense. In the end it's not a huge deal, just that, as I understand it standard genealogy entry criteria are for the date to be presented as 10 Feb 1901, not 10 February 1901.

Teresa

Teresa,
"...I did, however, have one more question. I prefer my dates to be 02 Feb 1806, yet I FH automatically expands the month to its full version. I can't seem to find anywhere in the preferences to reset that. Is this possible? If not, it's not a huge deal breaker..."

Your dates will have Type - Date which will auto expand as you note above. Convenient for date entry and it can be changed but in a basic manner and with downsides. In the Source Template Definition (Custom/Editable) window double click on your date field and the Source Template Field Definition dialogue will open. Change Type to Text and OK to close then Save. You then have your date in whatever format you want as text BUT lose auto expand i.e. qualifiers like {Your_Date:YEAR} etc etc. You would also have to re-enter all dates wherever the template has been used.

Help > Source Template Formats is a good place to start.

[tatewise]

FYI: FH does use the standard GEDCOM format 10 FEB 1901 internally.

[fhtess65]

Ah...I'm just used to entering dates in that format everywhere and prefer to have dates presented that way in reports. But, in the end, it's not a huge deal. And now I know to use a text rather than a date field if I want to have it seen that way in reports etc.

T

FYI: FH does use the standard GEDCOM format 10 FEB 1901 internally.