Re: [pgsql-hackers] Re: Translations at pgfoundry

This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.

--8323328-1289712166-1106348119=:30770
Content-Type: TEXT/PLAIN; CHARSET=iso-8859-9; format=flowed
Content-Transfer-Encoding: 8BIT
Content-ID: <Pine(dot)LNX(dot)4(dot)61(dot)0501220056171(dot)30770(at)emo(dot)org(dot)tr>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On Fri, 21 Jan 2005, Josh Berkus wrote:

>>> OK, is anyone opposed to this idea?  I would register a pgfoundry
>>> project (name suggestions? "translations"?), give most established
>>> translators commit access, and move the statistics pages there.
>
> BTW, there is already a "translators" mailing list. While I've been using it
> for the press releases, there's no reason why the translators can use it for
> all translations.

Are all regional contacts are also the translators of .po files?

Translating a press release is somewhat a non-technical issue; but the .po
translators have to know PostgreSQL internals, I think... So, translators
ml should be limited to the press release translators as it is now; and we
need to create a new ml for the .po translators.

Just my 0.02 ...

Regards,
- --
Devrim GUNDUZ
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.tdmsoft.com http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFB8Ymdtl86P3SPfQ4RAp4zAJ918KcctE/c90xlA99/cI63wBn04gCdF5RQ
ooljgkP59MdcRSrr98AjBzE=
=QgSX
-----END PGP SIGNATURE-----
--8323328-1289712166-1106348119=:30770--