The Hermit Hacker wrote:
>
> Hrmmm...create an 'include/utils/errmsg.h file that is a link created by
> configure based on a --with-language=<insert your language here>...the
> file would contain:
>
> #define <ERRMSG TOKEN> "Error message in your language"
^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Then use the TOKEN with elog...
>
> If we did something like this, we wouldn't have to convert all at once
> either, just as we pick up a new one...
Sometime ago we told about using error codes in elog (and put them to the
client) - this would very useful for non-interactive applications...
How about to implement this ?
Vadim