Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	msnyder@vmware.com, 	gdb-patches@sourceware.org
Subject: Re: [RFA] [patch] 'info symbol' to print more info
Date: Wed, 19 Nov 2008 04:20:00 -0000	[thread overview]
Message-ID: <20081118210101.GB3838@adacore.com> (raw)
In-Reply-To: <8ac60eac0811171536m1ac412f0k934c5acd5a1cc1f4@mail.gmail.com>

> 2008-11-17  Paul Pluzhnikov  <ppluzhnikov@google.com>
> 
> 	* objfiles.h: New MULTI_OBJFILE_P macro.
> 	* printcmd.c (sym_info): Print object name.
> 	* maint.c (maintenance_translate_address): Likewise.

Just one comment.

> testsuite/ChangeLog
> 2008-11-17  Paul Pluzhnikov  <ppluzhnikov@google.com>
> 
> 	* gdb.base/sepsymtab.exp: Update for new 'info sym' format.

This part looks ok to me.

> +	mapped = section_is_mapped (osect) ? "mapped" : "unmapped";

This part needs to be marked for translation as well.

> +	if (MULTI_OBJFILE_P ())
> +	  if (pc_in_unmapped_range (addr, osect))
> +	    if (section_is_overlay (osect))
> +	      printf_filtered (_("%s + %u in load address range of "
> +				 "%s overlay section %s of %s\n"),
> +			       msym_name, offset,
> +			       mapped, sec_name, obj_name);

I just want to make sure that others would agree that the "%s overlay
section" would not cause any problem for the translators. I tried to
use French as an example, and although my translation is horrible
because I don't know the French terms for these technical concepts,
I think it still showed me that it worked:

  %s + %u par rapport au bloc d'addresse de la section overlay %s dans %s

where "mapped" would have been translated to "mappée".

Anyway, as far as I can tell, as long as "mapped" and "unmapped"
are marked for translation, the patch looks good to me.

-- 
Joel


  parent reply	other threads:[~2008-11-18 21:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-15 16:15 Paul Pluzhnikov
2008-11-15 17:00 ` Michael Snyder
2008-11-15 17:22   ` Paul Pluzhnikov
2008-11-15 18:51     ` Michael Snyder
2008-11-15 23:16       ` Paul Pluzhnikov
2008-11-15 23:35         ` Andreas Schwab
2008-11-16  1:35         ` Eli Zaretskii
2008-11-16  1:38           ` Paul Pluzhnikov
2008-11-16  8:20             ` Joel Brobecker
2008-11-17 22:37               ` Paul Pluzhnikov
2008-11-17 23:35                 ` Daniel Jacobowitz
2008-11-18 16:07                   ` Paul Pluzhnikov
2008-11-18 19:55                     ` Eli Zaretskii
2008-11-19  4:20                     ` Joel Brobecker [this message]
2008-11-19 12:45                       ` Paul Pluzhnikov
2008-11-15 17:40 ` Eli Zaretskii

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=20081118210101.GB3838@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=ppluzhnikov@google.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