| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Call for translations |
| Date: | 2020-10-12 06:33:30 |
| Message-ID: | ce2de659-ead9-fd07-51af-f918ce91a08a@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello,
I would like to remind everyone about the PostgreSQL message translation
effort and invite those capable of contributing to join in. Several
once-well maintained languages have fallen by the wayside a bit lately,
and of course there is always the possibility of starting a new language
or reviewing and revising work in existing languages.
If you want to help, see <https://babel.postgresql.org/> for status,
instructions, and other information. If there are already active
translation teams, please communicate with them first. The mailing list
<pgsql-translators(at)lists(dot)postgresql(dot)org> is available for general
discussion and coordination of translation activities.
The time is now. Even though PostgreSQL 13 was just released,
translation updates for the PostgreSQL 13 stable branch are still welcome.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Sterritt | 2020-10-12 13:35:41 | Re: PostgreSQL processes use large amount of private memory on Windows |
| Previous Message | Michael Paquier | 2020-10-12 00:16:54 | Re: rum index supported on pg13? |