Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: RFC 2646
Date: 06 Nov 1999 21:54:51 +0100	[thread overview]
Message-ID: <m3iu3fuyqs.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <rjhfk0qlkf.fsf@feller.dina.kvl.dk>

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> After pGnus is released, I think RFC 2646 support would be a good
> thing to work on.  It solves some of the worst shortcommings of
> text/plain in a backward compatible way.

(Executive summary: One encodes whether line break are "hard" or not
by using trailing whitespace.)

Yes, I think Gnus should support this if it becomes supported by any
other significant news/mail reader.

I don't think it will be, though.  It addresses one (annoying) aspect
of variable-width composition, and that's all it does, so I doubt that 
it's sexy enough to garner much enthusiasm.

> We might even invent a new format value for our _fancy_ markup.

Cursory reading of the rfc seems to say that the only valid values for
the FORMAT parameter are "fixed" and "flowed".  Adding more (sub)types
will require "fixed-and-fancy", "flowed-and-fancy", "fixed", "flowed",
and when people add more of these subformats, it'll expand
exponentially.  Which is one thing I don't like about this RFC; it
seems so... fixed.  No possibilty for future feepurism.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen


  parent reply	other threads:[~1999-11-06 20:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-09 21:19 Per Abrahamsen
1999-10-11  8:06 ` Steinar Bang
1999-10-11  8:11   ` Steinar Bang
1999-10-11 13:06     ` Per Abrahamsen
1999-10-12  8:19       ` Steinar Bang
1999-10-11 12:08 ` Toby Speight
1999-10-11 13:11   ` Per Abrahamsen
1999-11-06 20:54 ` Lars Magne Ingebrigtsen [this message]
1999-11-06 21:23   ` Per Abrahamsen
1999-11-07  3:22     ` Lars Magne Ingebrigtsen

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=m3iu3fuyqs.fsf@quimbies.gnus.org \
    --to=larsi@gnus.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;
as well as URLs for NNTP newsgroup(s).