Chris,
You're first variation, "<, d. <[S:PD:L], [S:PD:D]|[S:PD:L]|[S:PD:D]>>", works in that the sentence template does not add a trailing comma where there is a place but no date. However, there is a trailing comma. What gives?
Gedcom Publisher (GP) and GedSite (GS) follow a convention where locations with multiple parts that are separated by commas, such as "Boston, Massachusetts", get a trailing comma when added to a sentence. So, the value of [L] is "Boston, Massachusetts," not "Boston, Massachusetts". The comma is not added unless the place value has an internal comma. So, there is no trailing comma for "Boston", but there is a trailing comma for "Boston, Massachusetts".
In your example, when [S:PD:D] is empty, GP will choose the 2nd alternative, [S:PD:L]. The value will be the place text plus a trailing comma (in most cases).
What if you don't want that trailing comma for some reason?
You can add the NS parameter to the L reference to prevent the addition of the comma suffix: "<, d. <[S:PD:L], [S:PD:D]|[S:PD:L:NS]|[S:PD:D]>>"
FYI: You don't have to worry about the comma suffix when the place reference is at the end of a sentence. When GP and GS add text to a sentence, they adjust punctuation at "seams".
John Cardinal
Products: ORA, GedSite, Gedcom Publisher, Second Site, TMG Utility, TMG to GEDCOM
Web Hosting for Genealogists: Family History Hosting
--
Gedcom Publisher: https://www.gedcompublisher.com
GedSite: https://www.gedsite.com
---
You received this message because you are subscribed to the Google Groups "Gedcom Publisher" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gp-l+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gp-l/000b01da8ff5%243cbfe760%24b63fb620%24%40gmail.com.