From: | Peter T Mount <psqlhack(at)retep(dot)org(dot)uk> |
---|---|
To: | David Gould <dg(at)illustra(dot)com> |
Cc: | Vadim Mikheev <vadim(at)krs(dot)ru>, andreas(dot)zeugswetter(at)telecom(dot)at, hackers(at)postgresql(dot)org, mimo(at)interdata(dot)com(dot)pl |
Subject: | Re: [HACKERS] error messages not only English |
Date: | 1998-05-26 18:10:31 |
Message-ID: | Pine.LNX.3.95.980526190904.1473D-100000@retep.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 26 May 1998, David Gould wrote:
> Vadim writes:
> > Andreas Zeugswetter wrote:
> > >
> > > Anyway, we are still missing the first step in this direction: enumerate ERROR messages.
> >
> > BTW, are error codes in standard ?
>
> Some are. There is also a format for standard severity levels etc.
>
> On the internationalized message topic, how about storing all the messages
> in a text file. This file would be opened (but not read) at startup by each
> backend (and the postmaster). To change languages, just open a different
> file. ELOG would scan the message file to get the message text corresponding
> to an errog code. Since reading a pre-opened text file does not depend on
> much of the system working, it should work even in the catastrophic cases.
Do you want me to post a brief outline on how Java does this? It uses
plain text files to handle internationalized messages, and can handle
regional dialects as well?
--
Peter T Mount peter(at)retep(dot)org(dot)uk or petermount(at)earthling(dot)net
Main Homepage: http://www.retep.org.uk
************ Someday I may rebuild this signature completely ;-) ************
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter(at)maidstone(dot)gov(dot)uk
From | Date | Subject | |
---|---|---|---|
Next Message | Vadim Mikheev | 1998-05-26 18:16:24 | [Fwd: [ANNOUNCE] ipaddr data type - EXTENDED VERSION HERE] |
Previous Message | Peter T Mount | 1998-05-26 18:07:35 | Re: [GENERAL] RE: [HACKERS] error messages not only English |