Re: Translation of Documents in DDP in Korean
- To: Yooseong Yang <email@example.com>
- Cc: Adam Di Carlo <firstname.lastname@example.org>, email@example.com
- Subject: Re: Translation of Documents in DDP in Korean
- From: Josip Rodin <firstname.lastname@example.org>
- Date: Sun, 1 Oct 2000 12:32:44 +0200
- Message-id: <20001001123244.B19933@cibalia.gkvk.hr>
- In-reply-to: <20001001113109.A1633@pcel3.snu.ac.kr>; from email@example.com on Sun, Oct 01, 2000 at 11:31:09AM +0900
- References: <20000925163114.A22594@pcel3.snu.ac.kr> <firstname.lastname@example.org> <20000930133411.A16979@pcel3.snu.ac.kr> <email@example.com> <20001001113109.A1633@pcel3.snu.ac.kr>
On Sun, Oct 01, 2000 at 11:31:09AM +0900, Yooseong Yang wrote:
> > > What debian pakages do all DDP documents split into ?
> > Hmm, I'm not sure, offhand. I'd have to look.
> > BTW, the structure of how to do trasnlated documents does require some
> > thought. For instance, in developers-reference, which I maintain, I
> > have japanese and french versions within the package. That allows me
> > to share information between the translations and makes the
> > translators job easier. The idea is that I build all the
> > translations, making packages such as developers-reference-ja,
> > developers-reference-fr, etc.
> I am not clear to your idea. You mean you made pakages such as
> developers-reference-ja, -fr??
The point is that you can give the translation to the developer who
maintains the original version, so he can makes packages for it. That way,
your translation gets packaged quicker, the maintainer takes care it doesn't
get too outdated, and you don't have to go through the new-maintainer
It is how maint-guide* packages are done, too.
> To become a maintainer of one pakage is difficult??
Not necessarily, but you do have to pass the lengthy new-maintainer process.
Read http://www.debian.org/devel/join/newmaint , it has all the details.
Digital Electronic Being Intended for Assassination and Nullification