Re: RFC: Clean up "show remote"

[Eli Zaretskii <eliz@gnu.org>]

> Date: Mon, 23 Jan 2006 00:15:44 -0500
> From: Daniel Jacobowitz <drow@false.org>
> 
> > With your change, the part in parentheses will not be displayed, so
> > how would the user know that Z0 is a packet that sets software
> > breakpoints?
> 
> Instead, you'll get something that looks like the current output of
> "show print":
> 
> software-breakpoint-packet: Support for the `Z0' packet is auto-detected, currently unknown

Right, I didn't catch the part before the colon, since it's in another
place in the code.

But doesn't the above looks backwards, English-wise? we first announce
the full packet name, and then say that support for its short alias is
<whatever>.  The "foo: Bar" syntax is usually reserved for messages
that come from `foo', which is not really the case here.

> I'm trying to cut down on how badly this wraps, since we can't
> word-wrap in translated messages (is there any way to do that?

The only good way is to break it into two separate messages and mark
them in i18n comments as belonging to the same phrase.  Translators
will then break the translated message as appropriate for their
language (or even produce a single line, by translating the second
part as an empty string).

> GCC seems to wrap using spaces even in i18n output; maybe we
> could do the same, if I am interpreting that right?).

If that's what GCC does, GCC is not doing TRT: wrapping on spaces
works for Latin and other similar languages, but can be dead wrong in
other scripts.