From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Special characters in doc strings of GDB commands
Date: Mon, 12 Feb 2007 17:25:00 -0000 [thread overview]
Message-ID: <20070211204309.GA3751@nevyn.them.org> (raw)
In-Reply-To: <uk5yo5u0a.fsf@gnu.org>
On Sun, Feb 11, 2007 at 10:17:25PM +0200, Eli Zaretskii wrote:
> Right. Another possibility would be to enclose the short description
> part in some control sequence, which will be stripped by the commands
> that print the doc strings. For example, like makeinfo uses ^[..^]
> for similar purposes.
I guess that's better for translation purposes (tell translators to
leave those untranslated)? It still seems problematic, e.g. if the
natural phrasing of the long descripton doesn't have the short
description as a substring.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-11 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 11:37 Eli Zaretskii
2007-02-10 20:47 ` Daniel Jacobowitz
2007-02-11 4:13 ` Eli Zaretskii
2007-02-11 18:09 ` Daniel Jacobowitz
2007-02-11 20:17 ` Daniel Jacobowitz
2007-02-11 20:43 ` Eli Zaretskii
2007-02-12 3:11 ` Eli Zaretskii
2007-02-12 17:25 ` Daniel Jacobowitz [this message]
2007-02-12 17:58 ` Jim Blandy
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=20070211204309.GA3751@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.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