Proceeding with gettext
От | Peter Eisentraut |
---|---|
Тема | Proceeding with gettext |
Дата | |
Msg-id | Pine.LNX.4.30.0105291907500.757-100000@peter.localdomain обсуждение исходный текст |
Ответы |
Re: Proceeding with gettext
|
Список | pgsql-hackers |
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
В списке pgsql-hackers по дате отправления: