Re: [COMMITTERS] pgsql/src/test/regress/expected (plpgsql.out inet.out foreign_key.out errors.out)

> Bruce Momjian writes:
>
> > > Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > > > Speaking of error messages, one idea for 7.2 might be to prepended
> > > > numbers to the error messages.
> > >
> > > Isn't that long since on the TODO list? I know we've had long
> > > discussions about a thoroughgoing revision of error reporting.
> >
> > Yes. We have:
> >
> > * Allow elog() to return error codes, not just messages
> > * Allow international error message support and add error codes
> >
> > I just thought I would mention it is on my radar screen now.
>
> Yeah, it's on mine too. The only thing I'm still unsure about the
> "international" part. Does anyone know of a gettext-ish thing that has an
> acceptable license?

Yes, they must exist. I want a solution that doesn't make it difficult
for people add error messages. Having codes in the C files and error
messages in another file is quite a pain. My idea would enable us to
number the error messages, keep the English text for the message in the
same file next to the code, then allow international support by creating
a utility that can dump out all the codes with the Engligh text to allow
translators to make non-English versions. The translated file can then
be used by the backend to generate messages in other languagues using a
SET command.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026