git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Erik Faye-Lund <kusmabite@gmail.com>,
	Jonathan Nieder <jrnieder@gmail.com>
Subject: Bikeshedding advice on the ab/i18n-scripts series
Date: Mon, 16 May 2011 18:03:30 +0200	[thread overview]
Message-ID: <BANLkTi==pxyy7OeZT0mn33iJHrc5R7vHBw@mail.gmail.com> (raw)

On Wed, May 11, 2011 at 22:24, Junio C Hamano <gitster@pobox.com> wrote:

> Will merge to "master" by the end of week #3.
>
> * ab/i18n-scripts (2011-05-08) 48 commits
>  - i18n: git-bisect bisect_next_check "You need to" message
>  - i18n: git-bisect [Y/n] messages
>  - i18n: git-bisect bisect_replay + $1 messages

I'm now mostly done solving all the bugs noted in this series, aside
from the case insensitive env vars on win32 issue.

I know how to fix these, but some people may have issues with my style
of doing so, so I'd like to ask in advance to save me extra work.

Basically for code like this:

        while [ $# -gt 0 ]; do
            arg="$1"
            case "$arg" in
            --)
                shift
                break
                ;;
            *)
                rev=$(git rev-parse -q --verify "$arg^{commit}") || {
                    test $has_double_dash -eq 1 &&
                        die "$(eval_gettext "'\$arg' does not appear
to be a valid revision")"
                    break

I was thinking of just doing:

    WHATEVER_arg=$arg
    die "$(eval_gettext "'\$WHATEVER_arg' does not appear to be a
valid revision")"

Where WHATEVER is a sufficiently unique prefix. E.g.:

    WINDOWS_ME_HARDER
    GIT_I18N_VARIABLE
    YOUR_MOM
    DUDE_WHERES_MY_POSIX_COMPLIANCE

I'll just pick one at my discretion (not necessarily from that list)
unless someone has some strong preference. I don't care, I just don't
want to re-send it over that.

I could also change all occurances of "arg" (including arg="$1" etc.)
to WHATEVER_arg, but that seems like overkill, and would make the code
hard to read, since you'd have WHATEVER all over the place.

Oh, and for all the convertion of:

    echo >&2 "$(gettext "foobar")"

I've already done:

    (
        gettext "foobar" &&
        echo
    ) >&2

Is that OK, or does someone have a strong preference (and wants me to
waste time on converting it) for:

    gettext "foobar" >&2
    echo >&2

Or something else?

Your friendly neighborhood i18n maintainer.

             reply	other threads:[~2011-05-16 16:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 16:03 Ævar Arnfjörð Bjarmason [this message]
2011-05-16 16:26 ` Bikeshedding advice on the ab/i18n-scripts series Jonathan Nieder
2011-05-16 20:45 ` Junio C Hamano
2011-05-16 20:53   ` Ævar Arnfjörð Bjarmason
2011-05-16 20:58   ` Junio C Hamano
2011-05-16 21:13     ` Ævar Arnfjörð Bjarmason
2011-05-16 21:26       ` Jonathan Nieder
2011-05-16 21:32         ` Ævar Arnfjörð Bjarmason
2011-05-16 21:40           ` 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='BANLkTi==pxyy7OeZT0mn33iJHrc5R7vHBw@mail.gmail.com' \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=kusmabite@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;
as well as URLs for NNTP newsgroup(s).