Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Baurjan Ismagulov <ibr@ata.cs.hun.edu.tr>,
	gdb-patches@sources.redhat.com
Subject: Re: an i18n sample
Date: Sun, 12 Dec 2004 21:07:00 -0000	[thread overview]
Message-ID: <41BCA070.2030805@gnu.org> (raw)
In-Reply-To: <20041212183458.GA14438@nevyn.them.org>

> Baurjan did not preserve the existing style of concatenation; he
> changed it to be uniform, to the one I object to (for the reasons I
> gave).  If you disagree with my reasons, then let's discuss that
> instead of you executively overriding them.  Neither the GNU nor GDB
> coding style expresses a preference here.  Baurjan and I both prefer
> the concatenation style for aesthetic reasons and no one else chose to
> express an opinion.

We've previously discussed this and in the end we each [hopefully] 
accepted that there were technical and aesthetic reasons both for and 
against each choice (the ``agree to disagree'').

For shorter one line strings, there's no reason to retain the old style. 
  However, for longer multi-line strings, which need to be kept to 80 
columns, and require other white space formatting, then the old style is 
easier (and even when it breaks -p).

Remember, the Objective is to just get the strings marked up and then 
with the minimum of effort.  This isn't the time to be changing string 
styles.

Does that sound reasonable?

Andrew

PS: I was simply obliging Baurjan's request that his patch get committed.

PPS: Of course if someone were to add i18n wordwrap code that 
automatically split these paragraphs at convenient points, this whole 
debate would be mute.


  reply	other threads:[~2004-12-12 19:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-24 10:45 Baurjan Ismagulov
2004-10-24 19:28 ` Eli Zaretskii
2004-10-24 19:57   ` Baurjan Ismagulov
2004-10-24 20:18   ` Daniel Jacobowitz
2004-10-25 20:10     ` Eli Zaretskii
2004-10-25 20:20       ` Daniel Jacobowitz
2004-10-26  4:47         ` Eli Zaretskii
2004-10-26 20:02           ` Daniel Jacobowitz
2004-10-27  5:03             ` Eli Zaretskii
2004-10-25 21:59   ` Andrew Cagney
2004-10-26  5:02     ` Eli Zaretskii
2004-10-26  7:54       ` Baurjan Ismagulov
2004-10-26 19:56         ` Eli Zaretskii
2004-10-27 17:28           ` Andrew Cagney
2004-11-27 20:54 ` Baurjan Ismagulov
2004-11-27 22:18   ` Eli Zaretskii
2004-11-27 22:54     ` Baurjan Ismagulov
2004-12-04 19:55     ` Baurjan Ismagulov
2004-12-04 22:31       ` Baurjan Ismagulov
2004-12-12 17:12         ` Andrew Cagney
2004-12-12 18:42           ` Daniel Jacobowitz
2004-12-12 21:07             ` Andrew Cagney [this message]
2004-12-13  3:37               ` Eli Zaretskii
2004-12-04 23:04       ` Eli Zaretskii
2004-12-05 23:46     ` 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=41BCA070.2030805@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ibr@ata.cs.hun.edu.tr \
    /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