From: Erik Faye-Lund <kusmabite@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH/RFC 0/2] use libcharset.h with gettext if available
Date: Tue, 28 Sep 2010 23:47:38 +0200 [thread overview]
Message-ID: <AANLkTinxSqPD8H4Giigb1vbi7DC2wpDVqWmXGVZXmeKQ@mail.gmail.com> (raw)
In-Reply-To: <1285698577-28395-1-git-send-email-avarab@gmail.com>
On Tue, Sep 28, 2010 at 8:29 PM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> Yeah, I'm hoping it'll get into next soon so we can get more
> reports/fixes like these. Anyway, I amended your patches a bit, here
> are the changes:
>
> * Split up the s/char*/const char*/ change into its own patch, or is
> there a reason for why this needs to be there along with the
> libcharset.h change?
>
The reason was that my version of locale_charset() returns a const
char *, so I got a warning if I didn't. nl_langinfo() returns a char
*, so I don't think that constness-fix patch makes sense in itself.
But what might make more sense would be to squash it into the original
commit for that line.
> * Added docs about the define to the Makefile
>
Nice!
> * Added defaults for NO_LIBCHARSET to the default, I only changed the
> defaults for the MINGW entry, maybe it should be changed on Cygwin
> and Windows too? And probably on OpenBSD and NetBSD too.
>
I don't think NO_LIBCHARSET should be the default. libcharset is
reported to be a bit better than nl_langinfo at normalizing the
encoding, and GNU gettext depends on libcharset (through libiconv,
which libcharset is distributed with). So in the case of a GNU
gettext, libcharset should really be present.
> Erik Faye-Lund (2):
> gettext: use const char* instead of char*
> gettext: use libcharset when available
>
> Makefile | 17 +++++++++++++++++
> configure.ac | 6 ++++++
> gettext.c | 10 +++++++++-
> 3 files changed, 32 insertions(+), 1 deletions(-)
>
> --
> 1.7.3.159.g610493
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-09-28 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 16:05 [PATCH] gettext: use libcharset when available Erik Faye-Lund
2010-09-28 17:07 ` Ævar Arnfjörð Bjarmason
2010-09-28 17:42 ` Erik Faye-Lund
2010-09-28 18:29 ` [PATCH/RFC 0/2] use libcharset.h with gettext if available Ævar Arnfjörð Bjarmason
2010-09-28 21:47 ` Erik Faye-Lund [this message]
2010-09-29 10:00 ` Ævar Arnfjörð Bjarmason
2010-09-29 11:41 ` Erik Faye-Lund
2010-09-29 13:07 ` [PATCH] gettext: use libcharset when available Ævar Arnfjörð Bjarmason
2010-09-29 13:34 ` Erik Faye-Lund
2010-09-29 13:40 ` [PATCH v2] " Ævar Arnfjörð Bjarmason
2010-09-29 13:43 ` [PATCH v3] " Ævar Arnfjörð Bjarmason
2010-09-28 18:29 ` [PATCH/RFC 1/2] gettext: use const char* instead of char* Ævar Arnfjörð Bjarmason
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=AANLkTinxSqPD8H4Giigb1vbi7DC2wpDVqWmXGVZXmeKQ@mail.gmail.com \
--to=kusmabite@gmail.com \
--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).