Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@jprc.com>
Subject: Inserting attribution at a better point
Date: 08 Jul 1998 14:01:40 -0400	[thread overview]
Message-ID: <vxkvhp8ql17.fsf@pocari-sweat.jprc.com> (raw)

I was just reading/commenting in news.software.readers about the
problems of logically connecting attribution lines with a writers' own
text.  It seems to me that putting the attribution at the very top of
an article is not at all the right place; it should be put immediately
prior to the first unquoted text instead, to connect the writer with
his text better.

That is, the question revolves around the typical format...
________________

In article <123@foo.bar>, joe@schmo.net writes:
> In article <456@foo.bar>, jane@doe.org writes:

>> Jane's text goes here, which is appropriate because it's right
>> beside the attribution for her.

> Joe's text goes here, but it's now a significant distance from the
> attribution which identifies Joe.

New text continues hereafter.
________________

...versus a re-placement of the 1st attribution, farther into the
article, thus...
________________

In article <456@foo.bar>, jane@doe.org writes:
>> Jane's text goes here.

In article <123@foo.bar>, joe@schmo.net writes:
> Joe's text goes here, now closely connected to his attribution.

New text continues hereafter.
________________

Nth-level quotations make the problem of the 1st format all the worse,
because attributions get progressively farther from the text each
writer contributed to the resulting discussion.  Per-depth quotation
coloring helps, but does not solve this problem.  That's why I'd like
to see the 2nd format become possible in Gnus.

(I observe that I also take out the quotation `> ' from in front of
Jane's attribution line.  I'm not sure whether that is /really/
appropriate or not, but I confess that it's how I manually re-work
quotation format whenever I followup.)

How do others feel about this?

--karl


             reply	other threads:[~1998-07-08 18:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-08 18:01 Karl Kleinpaste [this message]
1998-07-08 22:20 ` Justin Sheehy
1998-07-09 10:36   ` Kai Grossjohann
1998-07-12  2:06     ` Lars Magne Ingebrigtsen
1998-07-12  3:06       ` Michael Harnois
1998-07-14  9:33       ` Kai Grossjohann
1998-07-14 21:02         ` Justin Sheehy
1998-07-15  7:32           ` Lars Magne Ingebrigtsen
1998-07-15 10:08           ` Kai Grossjohann
1998-07-15 12:06             ` Mats Lofdahl
1998-07-15 14:10               ` Lars Magne Ingebrigtsen
1998-07-16  8:02               ` Kai Grossjohann
1998-07-16  9:37                 ` Mats Lofdahl
1998-07-16  8:41                   ` Kai Grossjohann
1998-07-15 11:50           ` Kai Grossjohann

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=vxkvhp8ql17.fsf@pocari-sweat.jprc.com \
    --to=karl@jprc.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;
as well as URLs for NNTP newsgroup(s).