TMG-L Archives

Archiver > TMG > 2002-12 > 1040022032


From: Diana Powell <>
Subject: Re: [TMG] Sentence Help
Date: Sun, 15 Dec 2002 23:04:54 -0800
References: <3DFBCCA2.1070307@reigelridge.com> <3DFCEC9E.350C622C@sbcglobal.net> <3DFCF8F3.1090406@reigelridge.com> <3DFD11F9.3BE69EA2@sbcglobal.net> <005001c2a4c9$0da20960$d7b9fea9@MYRNICE>


Myrnice,
I seem to always be a little thick headed about these things and I
appreciate everyone's patience because I eventually do "get it". Your
statement below helped me figure out what I was seeing. The first comma
I was seeing was actually generated to follow the <[L]> variable, and
then the second comma was generated to precede the [PAR] variable.

template:
[P] was born <[D]> <[L]> <the [PAR]>

sentence:
Robert Hawk Moffett was born 30 May 1881 in Grundy Center, Iowa, the,
son of etc.

if the template is
[P] was born <[D]> <the [PAR]> then as you said there is only the comma
inserted before the PAR variable:

Robert Hawk Moffett was born 30 May 1881 the, son of etc.

So could there be a way, as Terry suggested, that the comma could be
overridden as we can override default prepositions within the
conditional brackets?

Thanks,
Diana

> There is only one comma/space inserted. It is inserted just before the [PAR]
> or [PARO] variable.
> There is also a space inserted after the name in the first tag if you use
> the [P] variable, or some other variation of the [P] variable.
>
> You are talking about placing data such as <the [PAR]> inside of conditional
> variables which will print out as "the, son of...". There is only one
> comma/space after the word "the" but it comes from the fact that the
> variable "[PAR]" supplied it.
>
> Myrnice
>
> "Diana Powell" wrote on Sunday, December 15, 2002 6:36 PM
> Subject: Re: [TMG] Sentence Help
>
> > Terry Reigel wrote:>
> > >
> > > I suspect the comma appears because the variable was invented for the
> > > marriage tag, and it was simple for that tag to have all the added
> > > phrase coded as part of the variable. They can't remove it now because
> > > of the millions of marriage tags users have created that would produce
> > > the wrong output if it was changed.
> >
> > That definitely makes sense for the first comma, eg. the one that
> > directly precedes the [PAR] or [PARO] variable, but the troublesome
> > comma is added AFTER the extra words inserted within the brackets
> > preceding [PAR]. I can't imagine a situation where anyone would want
> > both a comma before AND after an added word. The only situation where it
> > would be desireable is if you added a complete modifying phrase within
> > the brackets before [PAR] or [PARO], but I am having trouble thinking of
> > an example where that would be the case - especially in a template.
> >
> > It seems that what is happening is that TMG is coded for a comma before
> > [PAR] and [PARO] regardless of whether something is added within the
> > brackets or not - add a modifying word within the brackets and you get a
> > second comma. I'm not sure it would mess up existing marriage sentences
> > for anyone if the program only added a comma BEFORE the brackets
> > containing [PAR] or [PARO].
> > >
> > Diana P.
>
> ==== TMG Mailing List ====
> Send all messages and replies to <>.

This thread: