Thread: what's the meaning of the word "Tioga" in source
hi,
I'm translating those backend NLS strings, but I can't figure out
what's the meaning of the word "recipe" (I guess it's not the normal
meaning),
searching through the source, I found that they belong to
backend/tioga/tgRecipe.c,
but the source didn't give me any help, so ask here:
what's the meaning of the wrod "tioga", I think it's a abbreviation,
right?
then how to understand "recipe" here?
thanks & regards laser
On Sun, Feb 10, 2002 at 07:50:22PM +0800, Weiping He <laser@zhengmai.com.cn> wrote: > hi, > I'm translating those backend NLS strings, but I can't figure out > what's the meaning of the word "recipe" (I guess it's not the normal > meaning), > searching through the source, I found that they belong to > backend/tioga/tgRecipe.c, > but the source didn't give me any help, so ask here: > what's the meaning of the wrod "tioga", I think it's a abbreviation, > right? > then how to understand "recipe" here? While recipie might get used in an unusual context I think its basic meaning is pretty much always the same. It is a set of instructions for making something. (Most often some kind of prepared food.)
Weiping He <laser@zhengmai.com.cn> writes:
> I'm translating those backend NLS strings, but I can't figure out
> what's the meaning of the word "recipe" (I guess it's not the normal
> meaning),
> searching through the source, I found that they belong to
> backend/tioga/tgRecipe.c,
> but the source didn't give me any help, so ask here:
> what's the meaning of the wrod "tioga", I think it's a abbreviation,
> right?
It's just an old Berkeley project name without any particular meaning.
More to the point: the tioga code is all dead and unlikely to be
resurrected, as is everything to do with recipes in the backend.
You don't need to worry about translating anything that comes out
of that code.
Peter: it'd be a good idea to suppress gathering NLS messages out of
src/backend/commands/_deadcode/
src/backend/executor/_deadcode/
src/backend/optimizer/path/_deadcode/
src/backend/tioga/
as well as anything inside #ifdef NOT_USED. Dunno how difficult that
is with the gettext tools, though.
regards, tom lane
Ummm: http://citeseer.nj.nec.com/2143.html Tioga: A Database-Oriented Visualization Tool On Sun, 10 Feb 2002, Tom Lane wrote: > Weiping He <laser@zhengmai.com.cn> writes: > > I'm translating those backend NLS strings, but I can't figure out > > what's the meaning of the word "recipe" (I guess it's not the normal > > meaning), > > searching through the source, I found that they belong to > > backend/tioga/tgRecipe.c, > > but the source didn't give me any help, so ask here: > > what's the meaning of the wrod "tioga", I think it's a abbreviation, > > right? > > It's just an old Berkeley project name without any particular meaning. > > More to the point: the tioga code is all dead and unlikely to be > resurrected, as is everything to do with recipes in the backend. > You don't need to worry about translating anything that comes out > of that code. > > Peter: it'd be a good idea to suppress gathering NLS messages out of > src/backend/commands/_deadcode/ > src/backend/executor/_deadcode/ > src/backend/optimizer/path/_deadcode/ > src/backend/tioga/ > as well as anything inside #ifdef NOT_USED. Dunno how difficult that > is with the gettext tools, though. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/users-lounge/docs/faq.html >
Tom Lane writes: > Peter: it'd be a good idea to suppress gathering NLS messages out of > src/backend/commands/_deadcode/ > src/backend/executor/_deadcode/ > src/backend/optimizer/path/_deadcode/ > src/backend/tioga/ Or we could just remove those files. > as well as anything inside #ifdef NOT_USED. Dunno how difficult that > is with the gettext tools, though. It's not possible to deal with preprocessor macros. We know that NOT_USED will never be activated, but any other conditional might be a compile-time decision, so each branch needs to be considered. -- Peter Eisentraut peter_e@gmx.net
Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane writes:
>> Peter: it'd be a good idea to suppress gathering NLS messages out of
>> src/backend/commands/_deadcode/
>> src/backend/executor/_deadcode/
>> src/backend/optimizer/path/_deadcode/
>> src/backend/tioga/
> Or we could just remove those files.
That's a possibility too. I think it was Bruce's idea originally to
keep dead source files around, but I've never seen the point; isn't
that what CVS does for us?
regards, tom lane
On Sun, 10 Feb 2002, Tom Lane wrote: > Peter Eisentraut <peter_e@gmx.net> writes: > > Tom Lane writes: > >> Peter: it'd be a good idea to suppress gathering NLS messages out of > >> src/backend/commands/_deadcode/ > >> src/backend/executor/_deadcode/ > >> src/backend/optimizer/path/_deadcode/ > >> src/backend/tioga/ > > > Or we could just remove those files. > > That's a possibility too. I think it was Bruce's idea originally to > keep dead source files around, but I've never seen the point; isn't > that what CVS does for us? Okay, before you start removing this stuff, can someone take a look at the URL I sent around that actually talked about what TIOGA was meant for? My undestanding was that it was the underlying framework/code for a Data Visualization tool, which doesn' sound like how you described it :(
Tom Lane wrote: > Peter Eisentraut <peter_e@gmx.net> writes: > > Tom Lane writes: > >> Peter: it'd be a good idea to suppress gathering NLS messages out of > >> src/backend/commands/_deadcode/ > >> src/backend/executor/_deadcode/ > >> src/backend/optimizer/path/_deadcode/ > >> src/backend/tioga/ > > > Or we could just remove those files. > > That's a possibility too. I think it was Bruce's idea originally to > keep dead source files around, but I've never seen the point; isn't > that what CVS does for us? No, I would like all those files removed. I think Marc objected to their removal. To me, keeping stuff around that isn't every going to be used just adds confusion. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
On Sun, 10 Feb 2002, Bruce Momjian wrote: > Tom Lane wrote: > > Peter Eisentraut <peter_e@gmx.net> writes: > > > Tom Lane writes: > > >> Peter: it'd be a good idea to suppress gathering NLS messages out of > > >> src/backend/commands/_deadcode/ > > >> src/backend/executor/_deadcode/ > > >> src/backend/optimizer/path/_deadcode/ > > >> src/backend/tioga/ > > > > > Or we could just remove those files. > > > > That's a possibility too. I think it was Bruce's idea originally to > > keep dead source files around, but I've never seen the point; isn't > > that what CVS does for us? > > No, I would like all those files removed. I think Marc objected to > their removal. To me, keeping stuff around that isn't every going to be > used just adds confusion. My only objection is that the Tioga stuff, from what I've seen of it, looks like something we might want to revive when/if someone has time ... but I could be tgotally mis-understanding what I've read about it too ...
In article <20020210172918.H1499-100000@mail1.hub.org>,
Marc G. Fournier <scrappy@hub.org> wrote:
>My only objection is that the Tioga stuff, from what I've seen of it,
>looks like something we might want to revive when/if someone has time ...
>but I could be tgotally mis-understanding what I've read about it too ...
It would STILL be in CVS for resurrection.
mrc
--
Mike Castle dalgoda@ix.netcom.com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc