TMG-L Archives
Archiver > TMG > 2003-02 > 1044209086
From: nick <>
Subject: [TMG] Re: Double commas in IN (TMG4.0d & 5.04)
Date: Sun, 02 Feb 2003 18:04:46 +0000
References: <200302021548.h12FmHp5026358@lists5.rootsweb.com>
Bo,
Thanks for your quick reply. Certainly it does remove the double
commas but then also removes the ability to mould the location sentence
to something a bit nicer. For example, if one uses "<at [L]>" but the
Detail field is empty then one ends up with something like "at London",
or "at New Zealand" which is far from satisfactory. With the separate
location fields one can create a sentence structure like < at
[DETAIL]><, in [CITY]><, [COUNTY]><, in [COUNTRY]> so that if a field is
empty it doesn't lead to such an inappropriate phrase.
Is the extra comma considered to be an intentional feature of TMG (at
the moment I can't see why) or an unintentional feature which is on the
list for change?
Nick
> nick wrote:
>
>> It is quite possible that there has been an extensive discussion of
>>this topic already. If so, please forgive this repetition.
>> I am finding that in Individual Narrative the contents of the [DETAIL]
>>field are affecting the number of commas that TMG is adding to a
>>sentence involving an address.
>> If the two adjacent fields [DETAIL] and [CITY] have something like "St
>>Johns Hospital" and "Sheffield" in them, then the sentence
>> <at [DETAIL]><, [CITY]>
>>reads, appropriately: "at St Johns Hospital, Sheffield"
>>
>> but if the [DETAIL] field contains its own comma, as in "St Johns
>>Hospital, Fulwood", then the sentence reads: "at St Johns Hospital
>>Fulwood,, Sheffield"
>>
>
> Bob Gillis wrote
> Nick, globally change the sentence to <at [L]> and you won't get the
> double commas. Those parts of the location that you don't want to print
> put exclusion marker before: Detail = St John's Hospital, Fullwood,
> City = Sheffield, County = -Yorkshire. It will print as "at St Johns
> Hospital
> Fulwood, Sheffield"
This thread: