pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Weiping He <laser@zhengmai.com.cn>
To: Peter Eisentraut <peter_e@gmx.net>
To: Roberto Mello <rmello@cc.usu.edu>
Cc: pgsql-docs@postgresql.org
Subject: Re: Translation of the documentation
Date: Thu, 10 Jan 2002 10:34:44 +0800
Message-ID: <004901c1997f$7dd6a5c0$d20101c0@T21laser> (raw)
References: <Pine.LNX.4.30.0201091300130.734-100000@peter.localdomain>


> Roberto Mello writes:
> 
> > 1) Can we contribute these docs to the PostgreSQL project?
> 
> In general, yes.  However, until there is an evident and sustained effort
> to keep these up to date, I'm not sure if we should keep them in the main
> source tree.
> 
> > 2) What flags do we need to add to the docbook sources? (so that
> >    "make pt-BR" could be done, for example)
> 
> As far as DocBook sources, you put a lang="pt_br" attribute in the
> top-level element.  As far as Makefiles, there are a couple of
> possibilities, depending on what becomes of 1).
> 
> > 3) Under what license(s) should/must the translation be put?
> 
> The current license?
> 
> Btw., are you sure what you are getting into?  A complete translation of
> the PG documentation is going to take an insane amount of time.  You might
> also be interested in doing some translation work on program messages.
> See <http://www.postgresql.org/~petere/nls.php;.
> 

Using cvs diff and patching little by little periodically would save many time
(althought still lots of work to do). I wish the documentation of different language
could be maintained somewhere using cvs, thus we could encourage users of
different languages to use it and make it better, in fact, I've done four version of it,
from 6.5, 7.0, 7.1 to 7.2, and it seems those docs did very well in pushing the usage 
of PostgreSQL in China.

And I wish the program messages could  stable sometime later,
especially those for backend, sometimes I'm doing `make update-po',
there many message merged in and create too many `fuzzy' ones, and it 
would take lots of time to fix that. I can understand that, because there are
many message still need to be done in source code, so I thing it's better
for 7.3 loop to finished the whole NLS support.

    regards    laser




view thread (11+ messages)  latest in thread

Message-ID: <004901c1997f$7dd6a5c0$d20101c0@T21laser>
Permalink:  ../004901c1997f$7dd6a5c0$d20101c0@T21laser/
Also on:    postgresql.org/message-id/004901c1997f$7dd6a5c0$d20101c0@T21laser

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: laser@zhengmai.com.cn, peter_e@gmx.net, rmello@cc.usu.edu
  Subject: Re: Translation of the documentation
  In-Reply-To: <004901c1997f$7dd6a5c0$d20101c0@T21laser>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox