From: "Jean-Noël AVILA" <jn.avila@free.fr>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Jiang Xin <worldhello.net@gmail.com>
Subject: Re: Compile error due to po/fr.po on old gettext in v2.21.0
Date: Mon, 25 Feb 2019 21:54:35 +0100 [thread overview]
Message-ID: <2933589.YIuU4JMJIj@cayenne> (raw)
In-Reply-To: <874l8rwrh2.fsf@evledraar.gmail.com>
On Monday, 25 February 2019 21:19:53 CET Ævar Arnfjörð Bjarmason wrote:
> On a NetBSD test box I have with msgfmt 0.14.4 v2.21.0 fails to compile.
>
> I didn't spot this in rc2 because b3225a4183 ("l10n: fr.po v2.21.0 rnd
> 2", 2019-02-13) along with the rest of i18n updates gets pulled in after
> all the RCs.
>
> I.e. this is because of the comments being parsed (fuzzy comments).
>
> The 0.14.4 gettext release was back in 2005, so presumably this is due
> to some GPLv3 allergy of NetBSD's. The OS version itself is 7.1,
> released a couple of years ago.
>
I kept the commented entries as a translation memory, even when they are
fuzzy.
Would unfuzzying these entries resolve the issue?
next prev parent reply other threads:[~2019-02-25 20:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 20:19 Compile error due to po/fr.po on old gettext in v2.21.0 Ævar Arnfjörð Bjarmason
2019-02-25 20:54 ` Jean-Noël AVILA [this message]
2019-02-25 20:59 ` Ævar Arnfjörð Bjarmason
2019-02-26 2:12 ` Jiang Xin
2019-02-25 21:14 ` [PATCH] l10n: fr.po unfuzzy commented entries Jean-Noël Avila
2019-02-25 22:42 ` Ævar Arnfjörð Bjarmason
2019-02-26 20:38 ` Jean-Noël AVILA
2019-02-26 20:54 ` [PATCH v2] l10n: fr.po remove obsolete entries Jean-Noël Avila
2019-02-27 3:44 ` Jiang Xin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2933589.YIuU4JMJIj@cayenne \
--to=jn.avila@free.fr \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=worldhello.net@gmail.com \
/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 NNTP newsgroup(s).