Last update: gnulib's tarball was uploaded on alpha.gnu.org in Bison's
directory, and pushed into the Translation Project
(https://translationproject.org/domain/gnulib.html). So using gnulib-po should
now make more sense (and I plan to have Bison use it).
Cheers!
Hi all,
> Le 7 déc. 2018 à 04:33, Bruno Haible a écrit :
>
> Hi Akim,
>
>>> Yes, it would be desirable that someone regularly (maybe once every 6 months
>>> or so) submits the gnulib .pot file to the TP.
>>>
>>> Volunteers?
>>
>> I'm looking into this.
>
> Thank you!!
For the records, I've
Hi Akim,
> > Yes, it would be desirable that someone regularly (maybe once every 6 months
> > or so) submits the gnulib .pot file to the TP.
> >
> > Volunteers?
>
> I'm looking into this.
Thank you!!
> Is `./gnulib-tool --create-megatestdir --dir=/tmp/gnulib-$(date +%F)` the
> right starting
> Le 1 déc. 2018 à 16:57, Bruno Haible a écrit :
>
> Hi Akim,
>
>> My understanding is that the last time gnulib was submitted for translation
>> was in 2011: https://translationproject.org/domain/gnulib.html.
>
> Yes, it would be desirable that someone regularly (maybe once every 6 months
Paul Smith wrote:
> It's also possible that different versions of gettext could generate
> slightly different POT files, so if committers have different versions
> installed you get "warring commits" which change them back and forth.
> I don't know if POT files have this issue but other files gene
Hi Benno,
> > Ah, you were assuming that the POT file is stored in the version control
> > system?
> > This is a practice that produces problems,
>
> What problems does this produce?
There are basically three ways to deal with generated files in the context
of a version controlled repository,
On Sun, 2018-12-02 at 15:38 +0100, Benno Schulenberg wrote:
> > Ah, you were assuming that the POT file is stored in the version
> > control system? This is a practice that produces problems,
>
> What problems does this produce? (Probably this was discussed
> earlier and elsewhere? Maybe have a
Op 02-12-18 om 13:10 schreef Bruno Haible:
> - Thus the interface between the package maintainers and the TP is simpler
> if
> the package maintainers submit a tarball to the TP.
Precisely. Furthermore, when following git, how is the translator to
know that a release is approaching and t
Op 01-12-18 om 17:00 schreef Bruno Haible:
> Akim has just moved some code from Bison to Gnulib. He writes:
>
>> Also, I feel sorry for Bison's translators when submitting modules to
>> gnulib: it's kind of throwing away their work; it would be great if there
>> were a means to preserve these tr
> Akim Demaille wrote:
>> maybe the translation project could work on top of git now?
No, I'm not going to do that. The TP is geared toward packages that
make releases. So I need a (prerelease) tarball that contains the
corresponding POT file.
Benno
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,
> Le 1 déc. 2018 à 20:47, Bruno Haible a écrit :
>
>> maybe the translation project could work on top of git now?
>
> This shift of work from the maintainers to the translation coordinator
> would require
> 1. that the translation coordinator installs whatever tooling is needed
> to buil
Akim Demaille wrote:
> > Yes, it would be desirable that someone regularly (maybe once every 6 months
> > or so) submits the gnulib .pot file to the TP.
> >
> > Volunteers?
>
> I personally do no such thing for Bison. As part of Bison's
> release procedure, an announcement message is generated
> Le 1 déc. 2018 à 17:36, Akim Demaille a écrit :
>
> I personally do no such thing for Bison. As part of Bison's
> release procedure, an announcement message is generated, with
> these headers:
>
> To: bison-patc...@gnu.org
> Cc: bug-bi...@gnu.org, help-bi...@gnu.org, Sébastien Villemot
>
> Le 1 déc. 2018 à 16:57, Bruno Haible a écrit :
>
> Hi Akim,
>
>> My understanding is that the last time gnulib was submitted for translation
>> was in 2011: https://translationproject.org/domain/gnulib.html.
>
> Yes, it would be desirable that someone regularly (maybe once every 6 months
[CCing the TP coordinator]
Hi Benno,
Akim has just moved some code from Bison to Gnulib. He writes:
> Also, I feel sorry for Bison's translators when submitting modules to gnulib:
> it's kind of throwing away their work; it would be great if there were a
> means to preserve these translations.
Hi Akim,
> My understanding is that the last time gnulib was submitted for translation
> was in 2011: https://translationproject.org/domain/gnulib.html.
Yes, it would be desirable that someone regularly (maybe once every 6 months
or so) submits the gnulib .pot file to the TP.
Volunteers?
Bruno
> Le 26 nov. 2018 à 07:18, Akim Demaille a écrit :
>
> Using a gnulib-po
> (https://www.gnu.org/software/gnulib/manual/html_node/Localization.html)
> makes a lot of sense: maximize the factoring of the translation effort across
> packages. I was moving Bison to use this, but that's a visibl
Salut à tous,
Using a gnulib-po
(https://www.gnu.org/software/gnulib/manual/html_node/Localization.html) makes
a lot of sense: maximize the factoring of the translation effort across
packages. I was moving Bison to use this, but that's a visible regression: way
too many translations are not a
19 matches
Mail list logo
