From: Bruno Haible <bruno@clisp.org>
To: Akim Demaille <akim.demaille@gmail.com>
Cc: bug-gnulib@gnu.org
Subject: Re: gnulib's translation
Date: Fri, 07 Dec 2018 04:33:01 +0100 [thread overview]
Message-ID: <1618741.a2mMl4h6ti@omega> (raw)
In-Reply-To: <4E8F9821-9E3F-4C04-ABF5-2BDA7A213A1E@gmail.com>
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 point?
No, this is overkill.
Even
./gnulib-tool --create-testdir --without-tests --dir=...
is overkill.
It's essentially two commands:
$ version=`git describe HEAD | sed -e 's/v0.1/4.0.0/' -e 's/-/./g'`
# or similar - make sure it's increasing,
# cf. https://translationproject.org/domain/gnulib.html
$ xgettext --keyword=_ --keyword=N_ \
--copyright-holder='Free Software Foundation, Inc.' \
--package-name=gnulib --package-version=$version \
--msgid-bugs-address='bug-gnulib@gnu.org' \
-o gnulib.pot \
`find lib -name '*.h' -o -name '*.c' | LC_ALL=C sort`
Bruno
next prev parent reply other threads:[~2018-12-07 3:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 6:18 gnulib's translation Akim Demaille
2018-12-01 11:50 ` Akim Demaille
2018-12-01 15:57 ` Bruno Haible
2018-12-01 16:36 ` Akim Demaille
2018-12-01 16:41 ` Akim Demaille
2018-12-01 19:47 ` Bruno Haible
2018-12-02 6:04 ` Akim Demaille
2018-12-02 12:10 ` Bruno Haible
2018-12-02 14:38 ` Benno Schulenberg
2018-12-02 15:55 ` Paul Smith
2018-12-02 16:47 ` Bruno Haible
2018-12-02 16:46 ` Bruno Haible
2018-12-02 14:31 ` Benno Schulenberg
2018-12-06 18:11 ` Akim Demaille
2018-12-07 3:33 ` Bruno Haible [this message]
2019-01-12 7:28 ` Akim Demaille
2019-02-05 19:09 ` Akim Demaille
2018-12-01 16:00 ` Bruno Haible
2018-12-02 14:27 ` Benno Schulenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1618741.a2mMl4h6ti@omega \
--to=bruno@clisp.org \
--cc=akim.demaille@gmail.com \
--cc=bug-gnulib@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).