Re: Proceeding with gettext

Peter, can you give a little sample of how an elog() call would look in
the new system?  Thanks.

> Has it been established to satisfaction that a BSD-licensed gettext
> implementation is available and working?  (Note that we still need
> xgettext and msgmerge from GNU, but this only on the maintainer side.)
> 
> Are there any other concerns about the use of the gettext API, the
> available implementations, or how this will work together with PostgreSQL?
> 
> If Yes and No, respectively, I'd like to put this to use.
> 
> Besides the source code changes to mark all translatable strings (which
> can be reduced if we make use of short cuts like "all calls to elog() are
> candidates"), and eliminate English dependent coding (printf("%d row%s",
> n, n!=1?"s":"");), most of this will be makefile work in the style of
> Makefile.shlib to take care of building, installing, and maintaining the
> message catalogs.  Plus a lot of translation work, of course.  :-)
> 
> -- 
> Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
> 

--  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,
Pennsylvania19026