Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: i18n, part 2
Date: Sat, 04 Dec 2004 21:52:00 -0000	[thread overview]
Message-ID: <20041204200605.GA15732@nevyn.them.org> (raw)
In-Reply-To: <20041204195702.GA25306@ata.cs.hun.edu.tr>

On Sat, Dec 04, 2004 at 08:57:02PM +0100, Baurjan Ismagulov wrote:
> * arm-tdep.c:_initialize_arm_tdep()
> 
>   The text "\
> When off, a 26-bit PC will be used.\n\
> When off, a 26-bit PC will be used." looked strange to me, is it
>   indended to be so?

When the help_doc argument was added to this function, a lot of uses
were converted in batch.  It looks like this one was just a typo.  Old
GDB would print:

(gdb) help show arm apcs32
Show usage of ARM 32-bit mode.  When off, a 26-bit PC will be used.

New GDB prints:

(gdb) help show arm apcs32
Show usage of ARM 32-bit mode.
When off, a 26-bit PC will be used.
When off, a 26-bit PC will be used.

[In the old interface, the whole thing was one translatable message. 
Now it is two, on separate lines.]

>  	      internal_error (__FILE__, __LINE__,
> -			      "arm_elf_osabi_sniffer: Unknown ARM EABI "
> -			      "version 0x%x", eflags);
> +			      _("arm_elf_osabi_sniffer: Unknown ARM EABI \
> +version 0x%x"), eflags);

GDB is already inconsistent about this, but does the "" "" style of
string concatenation cause any problem for gettext?  Otherwise, I
mildly prefer it - it prevents diff -p from getting confused about the
function name.


-- 
Daniel Jacobowitz


  reply	other threads:[~2004-12-04 20:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04 20:06 Baurjan Ismagulov
2004-12-04 21:52 ` Daniel Jacobowitz [this message]
2004-12-04 22:17   ` Baurjan Ismagulov
2004-12-04 23:59     ` Daniel Jacobowitz
2004-12-05 21:41     ` Eli Zaretskii
2004-12-05 23:39       ` Daniel Jacobowitz
2004-12-06  2:19         ` Baurjan Ismagulov
2004-12-06  4:59         ` Eli Zaretskii
2004-12-06  0:00       ` Baurjan Ismagulov
2004-12-15  0:50       ` Baurjan Ismagulov
2004-12-15 21:48         ` Eli Zaretskii
2004-12-06 18:53 ` Kevin Buettner
2004-12-06 20:59   ` Eli Zaretskii
2004-12-06 23:04     ` Kevin Buettner
2004-12-07  5:08       ` Eli Zaretskii
2004-12-07  5:10         ` Daniel Jacobowitz
2004-12-07 17:28         ` Kevin Buettner
2004-12-07 19:59           ` Eli Zaretskii
2004-12-07 20:28             ` Andreas Schwab
2004-12-12 19:50               ` Andrew Cagney
2004-12-12 22:08                 ` Eli Zaretskii
2004-12-12 18:23           ` Andrew Cagney
2004-12-12 21:49             ` Eli Zaretskii
2004-12-07 22:02         ` Eli Zaretskii
2004-12-12 18:35 ` Andrew Cagney
2004-12-26  4:46   ` Baurjan Ismagulov
2004-12-26 23:25     ` Eli Zaretskii
2005-01-05 15:48 ` Andrew Cagney
2005-01-05 16:07   ` Baurjan Ismagulov

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=20041204200605.GA15732@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.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