bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnulib's translation


From: Bruno Haible
Subject: Re: gnulib's translation
Date: Sun, 02 Dec 2018 13:10:47 +0100
User-agent: KMail/5.1.3 (Linux/4.4.0-138-generic; KDE/5.18.0; x86_64; ; )

Hi Akim,

> > This shift of work from the maintainers to the translation coordinator
> > would require
> >  1. that the translation coordinator installs whatever tooling is needed
> >     to build a particular package,
> 
> It is true that some of the messages might not be in the package
> itself, but I would expect that it's a common case that all the
> _() mark up is already available.

Yes, the POT file can usually be generated from the sources found in a git
repository. But I argue that it's not the job of the TP coordinator to
build all kinds of packages.

In other words:
  - In a version control repository you find: sources.
  - In a tarball you find: sources + generated files.
  - The POT file is a generated file.
  - Thus the interface between the package maintainers and the TP is simpler if
    the package maintainers submit a tarball to the TP.

> I was not suggesting that the
> TP would run code from the repo.  I guess I'm too naive thinking
> that enough information is available from a commit.

Ah, you were assuming that the POT file is stored in the version control system?
This is a practice that produces problems, and will be become rare after the
next gettext release.

Bruno




reply via email to

[Prev in Thread] Current Thread [Next in Thread]