From: Nick Clifton <nickc@redhat.com>
To: "Arsen Arsenović" <arsen@aarsen.me>,
gdb-patches@sourceware.org, binutils@sourceware.org
Cc: Bruno Haible <bruno@clisp.org>, Iain Sandoe <iain@sandoe.co.uk>
Subject: Re: [PATCH v2 2/2] *: suppress xgettext 0.22 charset name error
Date: Wed, 27 Sep 2023 16:21:13 +0100 [thread overview]
Message-ID: <9ede46ef-f5cb-d6e0-3abb-6b77252f8ead@redhat.com> (raw)
In-Reply-To: <20230926004300.1716711-4-arsen@aarsen.me>
Hi Arsen,
> bfd.po: warning: Charset "CHARSET" is not a portable encoding name.
> Message conversion to user's charset might not work.
> /usr/bin/xgettext: present charset "CHARSET" is not a portable encoding name
>
> As Bruno Haible <bruno@clisp.org> suggested:
>>> Perhaps it'd be good to use -o to suppress this warning anyway
>>
>> Yes, regardless of gettext version, you profit of the .pot suffix handling by
>> replacing
>>
>> --default-domain=$(PACKAGE)
>>
>> with
>>
>> -o $(PACKAGE)-tmp.pot
>>
>> (twice) and
>>
>> < $(PACKAGE).po > $@-t
>>
>> with
>>
>> < $(PACKAGE)-tmp.pot > $@-t
>
> bfd/ChangeLog:
>
> * po/Make-in ($(srcdir)/$(PACKAGE).pot): Output to a .pot
> temporary file, to suppress xgettext checking charset names.
>
> binutils/ChangeLog:
>
> * po/Make-in ($(srcdir)/$(PACKAGE).pot): Output to a .pot
> temporary file to suppress xgettext checking charset names.
>
> gas/ChangeLog:
>
> * po/Make-in ($(srcdir)/$(PACKAGE).pot): Output to a .pot
> temporary file to suppress xgettext checking charset names.
>
> gold/ChangeLog:
>
> * po/Make-in ($(srcdir)/$(PACKAGE).pot): Output to a .pot
> temporary file to suppress xgettext checking charset names.
>
> gprof/ChangeLog:
>
> * po/Make-in ($(srcdir)/$(PACKAGE).pot): Output to a .pot
> temporary file to suppress xgettext checking charset names.
>
> ld/ChangeLog:
>
> * po/Make-in ($(srcdir)/$(PACKAGE).pot): Output to a .pot
> temporary file to suppress xgettext checking charset names.
>
> opcodes/ChangeLog:
>
> * po/Make-in ($(srcdir)/$(PACKAGE).pot): Output to a .pot
> temporary file to suppress xgettext checking charset names.
This part of the patch set is approved as well.
Cheers
Nick
prev parent reply other threads:[~2023-09-27 15:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 0:17 [PATCH v2 0/2] Replace intl/ with out-of-tree GNU gettext Arsen Arsenović
2023-09-26 0:17 ` [PATCH v2 1/2] *: add modern gettext support Arsen Arsenović
2023-09-26 2:12 ` Kevin Buettner
2023-09-26 5:09 ` Tsukasa OI
2023-09-26 8:58 ` Nick Clifton
2023-09-26 13:55 ` Arsen Arsenović
2023-09-26 7:03 ` Jan Beulich
2023-09-26 7:54 ` Iain Sandoe
2023-09-26 14:44 ` Arsen Arsenović
2023-09-27 7:11 ` Jan Beulich
2023-09-27 13:06 ` Arsen Arsenović
2023-09-27 15:19 ` Nick Clifton
2023-09-27 17:43 ` Arsen Arsenović
2023-09-28 9:43 ` Nick Clifton
2023-09-29 15:58 ` Bruno Haible
2023-09-29 16:27 ` Arsen Arsenović
2023-11-20 16:42 ` Kévin Le Gouguec
2023-11-20 20:30 ` Arsen Arsenović
2023-11-20 21:28 ` Bruno Haible
2023-09-26 0:17 ` [PATCH v2 2/2] *: suppress xgettext 0.22 charset name error Arsen Arsenović
2023-09-27 15:21 ` Nick Clifton [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=9ede46ef-f5cb-d6e0-3abb-6b77252f8ead@redhat.com \
--to=nickc@redhat.com \
--cc=arsen@aarsen.me \
--cc=binutils@sourceware.org \
--cc=bruno@clisp.org \
--cc=gdb-patches@sourceware.org \
--cc=iain@sandoe.co.uk \
/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).