[pacman-dev] Documentation and manpages [was: Release Schedule for 3.0]

Roman Kyrylych roman.kyrylych at gmail.com
Wed Feb 7 04:37:45 EST 2007


2007/2/7, Aaron Griffin <aaronmgriffin at gmail.com>:
> On 2/6/07, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
> > On 2/6/07, Dan McGee <dpmcgee at gmail.com> wrote:
> > > This is a proposal to clean up our build system a bit. Currently, the
> > > translated manpages are generated using a tool called po4a, which
> > > seems to be a rather contrived way to generate just a few things.
> > > Would it be easier for translators to just translate the whole
> > > manpage, in its original form? This would greatly simplify this side
> > > of the documentation keeping, and we could develop a system to figure
> > > out when our translated manpages need updating.
> > >
> > > In addition, it seems to make sense to just move the manpages to their
> > > real name (pacman.8) instead of automake/autoconf input files
> > > (pacman.8.in). There isn't much reason to have these preprocessed.
> > >
> > > All of this would make working on the documentation a lot less
> > > intimidating, in my opinion. Thoughts?
> >
> > You already know I'm for it. Heh.
>
> Anyone else?

I never did any .po or man translation, but I think just making a copy
of manpage and translate it to another language will be much simpler
than with po4a.

-- 
Roman Kyrylych (Роман Кирилич)


More information about the pacman-dev mailing list