git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Michele Ballabio <barra_cuda@katamail.com>
Cc: Paul Mackerras <paulus@samba.org>, git <git@vger.kernel.org>
Subject: Re: gitk translation updates needed?
Date: Wed, 03 Feb 2010 14:20:12 -0800	[thread overview]
Message-ID: <7v636ec677.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <201002032156.16101.barra_cuda@katamail.com> (Michele Ballabio's message of "Wed\, 3 Feb 2010 21\:56\:15 +0100")

Michele Ballabio <barra_cuda@katamail.com> writes:

>>  $ make po/gitk.pot
>>  $ msgmerge -U po/it.po po/gitk.pot ;# and for other languages...
>>  $ make po/it.msg
>
> Yes, with these steps it.po now contains:
>
> #: gitk:2782
> #, fuzzy
> msgid ""
> "\n"
> "Gitk - a commit viewer for git\n"
> "\n"
> "Copyright ©9 2005-2009 Paul Mackerras\n"
> "\n"
> "Use and redistribute under the terms of the GNU General Public License"
>
> The "fuzzy" attribute is bogus but is understandable, because
> the msgid changed: "©" became "©9". What I don't get is:
> why "©" became "©9"? Was it a needed change or just an oversight?

Very interesting.

The last commit that touched the copyright line in gitk was aa43561 (gitk:
Don't compare fake children when comparing commits, 2009-09-10) that
updated the years.  But the commit did not change the circle-c symbol at
all:

    $ git show --format='%H' -U1 aa43561a | head -n 10 | tail -n 2 | od -cx
    0000000   -   #       C   o   p   y   r   i   g   h   t     302 251    
            232d 4320 706f 7279 6769 7468 c220 20a9
    0000020   2   0   0   5   -   2   0   0   8       P   a   u   l       M
    ...
    0000100   +   #       C   o   p   y   r   i   g   h   t     302 251    
            232b 4320 706f 7279 6769 7468 c220 20a9
    0000120   2   0   0   5   -   2   0   0   9       P   a   u   l       M

"make po/gitk.pot" which is "xgettext -kmc -LTcl -o po/gitk.pot gitk"
however produces this:

    $ grep Paul po/gitk.pot | od -cx
    0000000   "   C   o   p   y   r   i   g   h   t     302 251   9       2
            4322 706f 7279 6769 7468 c220 39a9 3220
    0000020   0   0   5   -   2   0   0   9       P   a   u   l       M   a
    ...

Notice that "302 251 9"?

Is this a bug in "gettext", perhaps?

  parent reply	other threads:[~2010-02-03 22:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 15:16 git-gui translation updates needed Shawn O. Pearce
2010-02-02 10:20 ` [PATCH] git-gui: update Japanese translation Nanako Shiraishi
2010-02-02 12:18 ` [PATCH] git-gui: update french translation Emmanuel Trillaud
2010-02-03  1:09 ` git-gui translation updates needed Junio C Hamano
2010-02-03  1:19   ` gitk translation updates needed? Junio C Hamano
2010-02-03 10:13     ` Michele Ballabio
2010-02-03 19:46       ` Junio C Hamano
2010-02-03 20:56         ` Michele Ballabio
2010-02-03 21:46           ` Paul Mackerras
2010-02-03 22:21             ` Junio C Hamano
2010-02-03 22:20           ` Junio C Hamano [this message]
2010-02-03 22:24             ` Junio C Hamano
2010-02-03 10:11   ` git-gui translation updates needed Michele Ballabio
2010-02-03 19:42     ` Junio C Hamano
2010-02-03 19:52       ` git-gui clone WTFery Shawn O. Pearce

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=7v636ec677.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barra_cuda@katamail.com \
    --cc=git@vger.kernel.org \
    --cc=paulus@samba.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).