git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Alexandre Erwin Ittner <alexandre@ittner.com.br>, git@vger.kernel.org
Subject: Re: Please pull gitk.git master branch
Date: Tue, 14 Dec 2010 08:03:17 +1100	[thread overview]
Message-ID: <20101213210317.GA10027@brick.ozlabs.ibm.com> (raw)
In-Reply-To: <7vbp4q5ddo.fsf@alter.siamese.dyndns.org>

On Sun, Dec 12, 2010 at 11:40:51PM -0800, Junio C Hamano wrote:
> Junio C Hamano <gitster@pobox.com> writes:
> 
> -- >8 --
> From: Junio C Hamano <gitster@pobox.com>
> Date: Sun, 12 Dec 2010 23:27:21 -0800
> Subject: [PATCH] Rename po/pt_BR.po to po/pt_br.po
> 
> The "msgfmt --tcl pt_BR.po" (at least on my box, GNU gettext 0.17) command
> generates pt_BR.msg, i.e. the country part gets downcased.  The resulting
> runtime (i.e. Tcl i18n) happily reads from pt_br.msg when run with the
> runtime locale set with LANG=pt_BR and/or LC_ALL=pt_BR so it seems to be
> the expected behaviour.
> 
> However, we seem to expect that the resulting file to be named pt_BR.msg,
> and try to generate and install it.
> 
> Currently our Makefile uses $(wildcard po/*.po) to grab the source PO
> files, expects them to produce $(subst .po,.msg,$(ALL_POFILES)), and its
> dependency rule is set to use "%.msg : %.po" pattern, all of which need
> to be adjusted with downcasing from po to msg files; the poor-man's msgfmt
> script also needs to learn the same downcasing.
> 
> Compared to that, renaming the input file to use lowercase countryname
> throughout the toolchain seems to be a lot cleaner solution to this
> glitch.
> 
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
>  po/{pt_BR.po => pt_br.po} |    0
>  1 files changed, 0 insertions(+), 0 deletions(-)
>  rename po/{pt_BR.po => pt_br.po} (100%)
> 
> diff --git a/po/pt_BR.po b/po/pt_br.po
> similarity index 100%
> rename from po/pt_BR.po
> rename to po/pt_br.po

Sorry about the glitch.  The renaming seems like the best idea, since
all the other .po files have lowercase names.  I was hoping to hear
Alexandre Erwin Ittner's opinion, though.

If I apply this patch in my repo, is that going to cause problems in
yours?  Or, since the commit that adds this file is the head commit, I
could just rewind it and reapply with the lowercase name.  Do you see
problems with that?

Paul.

  parent reply	other threads:[~2010-12-13 21:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12  6:31 Please pull gitk.git master branch Paul Mackerras
2010-12-12 23:20 ` Junio C Hamano
2010-12-13  3:11   ` Junio C Hamano
2010-12-13  7:40     ` Junio C Hamano
2010-12-13  8:36       ` Sverre Rabbelier
2010-12-13  9:25         ` Andreas Ericsson
2010-12-13 19:52         ` Andreas Schwab
2010-12-13 21:03       ` Paul Mackerras [this message]
2010-12-13 21:45         ` Junio C Hamano
2010-12-14  9:07           ` Paul Mackerras
2010-12-14 17:09             ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2010-01-29 11:59 Paul Mackerras
2010-01-29 20:57 ` 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=20101213210317.GA10027@brick.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=alexandre@ittner.com.br \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).