Mailinglist Archive: opensuse (3337 mails)

< Previous Next >
Re: [opensuse] Documentation required BEFORE release!
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Tue, 25 Apr 2006 12:45:13 +0200 (CEST)
  • Message-id: <Pine.LNX.4.61.0604251242100.21707@xxxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


The Tuesday 2006-04-25 at 12:09 +0200, David Wright wrote:

> > Impossible. You need the sources, and they are not included, you have to
> > downloaded them.
>
> You should write the documentation from the original specifications, not from
> the source code, same as writing test harnesses and test scripts. If you
> write from the specification, you are documenting what the program *should*
> do, which acts as a good double check that the code is doing what *it*
> should.

No, I don't mean that.

To translate a program you need the sources because the documentation you
see is the output of a postprocess. You need the sources of the
documentation. Also, for the step of translating the messages a program
gives you do need the source code. In theory, the .po file should be
enough, but you need the context.

- --
Cheers,
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFETf27tTMYHG2NR9URAktfAJ92nvlDbWpDKX38c6mtNhdBCX5jPgCfYnoK
pVYx5KpucOLeOKE3udgCw54=
=6hE8
-----END PGP SIGNATURE-----


< Previous Next >
Follow Ups