From: Brett Schwarz <brett_schwarz@yahoo.com>
To: Christian Stimming <stimming@tuhh.de>, Paul Mackerras <paulus@samba.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] gitk: Markup many strings for translation.
Date: Fri, 27 Jul 2007 13:19:08 -0700 (PDT) [thread overview]
Message-ID: <959247.27950.qm@web38905.mail.mud.yahoo.com> (raw)
>
> ----- Original Message ----
> From: Christian Stimming <stimming@tuhh.de>
> To: Paul Mackerras <paulus@samba.org>
> Cc: git@vger.kernel.org
> Sent: Friday, July 27, 2007 8:03:00 AM
> Subject: [PATCH 2/2] gitk: Markup many strings for translation.
>
> Similar to the discussion in git-gui, all user-visible strings are
> passed through the [mc ...] procedure to have them translated by msgcat.
>
> Signed-off-by: Christian Stimming <stimming@tuhh.de>
> ---
<snip>
> proc getcommitlines {fd view} {
> @@ -273,7 +273,7 @@ proc chewcommits {view} {
> #set ms [expr {[clock clicks -milliseconds] - $startmsecs}]
> #puts "overall $ms ms for $numcommits commits"
> } else {
> - show_status "No commits selected"
> + show_status [mc "No commits selected"]
> }
> notbusy layout
> set phase {}
> @@ -378,7 +378,7 @@ proc getcommit {id} {
> } else {
> readcommit $id
> if {![info exists commitinfo($id)]} {
> - set commitinfo($id) {"No commit information available"}
> + set commitinfo($id) {[mc "No commit information available"]}
I think this is probably a typo (on the original), and carrying that forward will probably result in what was not intended.
The original has the {} and "". I don't know if this was intended (it will keep the quotes).
The translated version, will result in a literal string [mc "No commit information available"], and unless it is explicitly eval'ed later, it will not result in the translated string.
So, if the quotes need to stay in the string, then the translation will have to be:
set commitinfo($id) \"[mc "No commit information available"]\"
Or, if the quotes are not needed:
set commitinfo($id) [mc "No commit information available"]
Regards,
--brett
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
next reply other threads:[~2007-07-27 20:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 20:19 Brett Schwarz [this message]
2007-07-28 2:40 ` [PATCH 2/2] gitk: Markup many strings for translation Paul Mackerras
2007-07-28 12:40 ` Christian Stimming
2007-07-28 12:52 ` [PATCH] gitk.git: Add Makefile with rules for po file creation Christian Stimming
-- strict thread matches above, loose matches on Subject: below --
2007-07-28 7:19 [PATCH 2/2] gitk: Markup many strings for translation Brett Schwarz
2007-07-27 14:53 [PATCH 1/2] gitk: Import msgcat for translation support Christian Stimming
2007-07-27 15:03 ` [PATCH 2/2] gitk: Markup many strings for translation Christian Stimming
2007-07-28 2:39 ` Paul Mackerras
2007-07-28 4:54 ` Junio C Hamano
2007-07-28 6:21 ` Paul Mackerras
2007-07-28 7:01 ` 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=959247.27950.qm@web38905.mail.mud.yahoo.com \
--to=brett_schwarz@yahoo.com \
--cc=git@vger.kernel.org \
--cc=paulus@samba.org \
--cc=stimming@tuhh.de \
/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.