All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Git List" <git@vger.kernel.org>,
	"Nguyễn Thái Ngọc" <pclouds@gmail.com>,
	"Andreas Schwab" <schwab@linux-m68k.org>
Subject: Re: [PATCH 2/2] i18n: Add extra -- to seperate gettext and message
Date: Fri, 15 Jun 2012 12:41:49 -0500	[thread overview]
Message-ID: <20120615174149.GG10752@burratino> (raw)
In-Reply-To: <CANYiYbGnoZDMkOq-goaPO98L4Ar1HzMVS-JjjBz7rNHVgv4ywQ@mail.gmail.com>

Jiang Xin wrote:

> I saw Ævar's bug report on xgettext to the GNU gettext list:
>
>  * http://git.661346.n2.nabble.com/GETTEXT-BUG-xgettext-1-can-t-extract-quot-gettext-foo-quot-td7560744.html
>
> May be post to a more official mailing list, such as bug-gnu-utils at
> https://lists.gnu.org/mailman/listinfo/bug-gnu-utils will get some response,

I think bug-gettext is the right place:
http://lists.gnu.org/archive/html/bug-gettext/2012-06/msg00003.html

> but I doubt there won't be a clear resolution in xgettext.

The double negative is leaving me confused. :)  Are you saying you
doubt that anyone will come up with a patch to fix xgettext, or that
you doubt that the result will be satisfactory?

[...]
> Write a wrapper for gettext  and extract messages using
> 'xgettext --keyword=<gettext-wrapper>' is a reasonable solution.

For what it's worth that does seem to me like the most sensible
workaround in the short term. :/

	gittext () {	# or sane_gettext or literal_gettext or something
		gettext -- "$1"
	}

	gittextln () {
		gettext -- "$1"
		echo
	}

Thanks,
Jonathan

  reply	other threads:[~2012-06-15 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-03 23:09 [PATCH 1/2] i18n: Extract msgs marked by sh gettext wrappers Jiang Xin
2012-06-03 23:09 ` [PATCH 2/2] i18n: Add extra -- to seperate gettext and message Jiang Xin
2012-06-04  8:56   ` Ævar Arnfjörð Bjarmason
2012-06-04 13:55     ` Jiang Xin
2012-06-04 16:59       ` Junio C Hamano
2012-06-15 16:05         ` Jiang Xin
2012-06-15 17:41           ` Jonathan Nieder [this message]
2012-06-15 18:13             ` Junio C Hamano

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=20120615174149.GG10752@burratino \
    --to=jrnieder@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.com \
    --cc=schwab@linux-m68k.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.