git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jean-Noël AVILA" <jn.avila@free.fr>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] l10n: fr.po unfuzzy commented entries
Date: Tue, 26 Feb 2019 21:38:43 +0100	[thread overview]
Message-ID: <7020728.IPHcI6cZlJ@cayenne> (raw)
In-Reply-To: <871s3vwkvw.fsf@evledraar.gmail.com>

On Monday, 25 February 2019 23:42:11 CET Ævar Arnfjörð Bjarmason wrote:
> 
> On Mon, Feb 25 2019, Jean-Noël Avila wrote:
> 
> > 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.
> 
> So this one pargaraph of commit message is just a paragraph from my
> E-Mail upthread, but out of context it's just confusing.
> 

Yes. More explanation.

> > -#, fuzzy
> > +#
> >  #~| msgid "git archive [<options>] <tree-ish> [<path>...]"
> >  #~ msgid "git diff --no-index [<options>] <path> <path>"
> >  #~ msgstr "git archive [<options>] <arbre ou apparenté> [<chemin>...]"
> 
> This still results in the same issue. Sorry, by "unfuzzying" I thought
> you meant change these translations so they'd no longer be commented out
> and would actually have a translation.
> 

The thing is that there isn't two msgid lines, the first one being the previous value.

> The problem is that there's two msgid lines, so e.g. this on top of
> yours "fixes" it:
> 
>      #
>     -#~| msgid "git archive [<options>] <tree-ish> [<path>...]"
>      #~ msgid "git diff --no-index [<options>] <path> <path>"
>      #~ msgstr "git archive [<options>] <arbre ou apparenté> [<chemin>...]"
> 
> But isn't a better fix on top of master just:
> 
>     sed -i '22477,$ d' po/fr.po
> 
> That results in 1500 lines removed from the end. I.e. what's the point
> of keeping those old now-unused translations around?

They can still be used as a translation memory for future approximate translations.

But, I guess it's safer to keep the translation memory out of this repo.

Will do.



  reply	other threads:[~2019-02-26 20:38 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
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 [this message]
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=7020728.IPHcI6cZlJ@cayenne \
    --to=jn.avila@free.fr \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.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 NNTP newsgroup(s).