Git development
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: kerylefondji7@gmail.com, git@vger.kernel.org
Cc: phillipwood123@gmail.com, gitster@pobox.com,
	christiancouder@gmail.com, siddharthasthana31@gmail.com
Subject: Re: [PATCH v2] archive-zip: refactor 'path too long' error message to use Q_()
Date: Tue, 20 Oct 2026 10:42:14 +0100	[thread overview]
Message-ID: <e06ea3e7-7555-42b9-8ea5-65e9d3b25281@gmail.com> (raw)
In-Reply-To: <20261019152725.714-1-kerylefondji7@gmail.com>

Hi Keryle

On 19/10/2026 16:27, kerylefondji7@gmail.com wrote:
> From: Keryle Fondji <kerylefondji7@gmail.com>
> 
> Replace _() with Q_() in the 'path too long' error message. Although
> pathlen is always greater than 0xffff when this error is hit, Q_() is
> required to support correct translation for languages that require
> different plural forms depending on the count.

This is good. As Junio has pointed out the code needs wrapping now that 
it is using Q_().

Thanks

Phillip

> Signed-off-by: Keryle Fondji <kerylefondji7@gmail.com>
> ---
>   archive-zip.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/archive-zip.c b/archive-zip.c
> index 6f73ca6d58..e4f8ef5a36 100644
> --- a/archive-zip.c
> +++ b/archive-zip.c
> @@ -328,7 +328,7 @@ static int write_zip_entry(struct archiver_args *args,
>   	}
>   
>   	if (pathlen > 0xffff) {
> -		return error(_("path too long (%d chars, SHA1: %s): %s"),
> +		return error(Q_("path too long (%d char, SHA1: %s): %s", "path too long (%d chars, SHA1: %s): %s", pathlen),
>   				(int)pathlen, oid_to_hex(oid), path);
>   	}
>   


      reply	other threads:[~2026-10-20  9:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1a15474a4114ba8b>
2026-10-19 15:27 ` [PATCH v2] archive-zip: refactor 'path too long' error message to use Q_() kerylefondji7
2026-10-20  9:42   ` Phillip Wood [this message]

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=e06ea3e7-7555-42b9-8ea5-65e9d3b25281@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=christiancouder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=kerylefondji7@gmail.com \
    --cc=phillip.wood@dunelm.org.uk \
    --cc=phillipwood123@gmail.com \
    --cc=siddharthasthana31@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