Gnus development mailing list
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
Cc: ding@gnus.org
Subject: Re: Gnus does not format my spam correctly!
Date: Tue, 22 Feb 2005 19:15:24 -0800	[thread overview]
Message-ID: <87d5usj7ar.fsf@codesourcery.com> (raw)
In-Reply-To: <87acpwkv0m.fsf@tc-1-100.kawasaki.gol.ne.jp> (Miles Bader's message of "Wed, 23 Feb 2005 08:57:45 +0900")

Miles Bader <miles@gnu.org> writes:

> Zack Weinberg <zack@codesourcery.com> writes:
>> The vertical bars were presumably intended to line up neatly, forming
>> a nice little table, but the spaces are too wide, or the horizontal
>> lines are too short, or both.  Confusion over which characters are
>> double-wide and which are single? Are the fonts not really
>> fixed-width?  Inquiring minds, &c.
>
> I think the people making this sort of thing are not usually well versed
> with the notion of "quality" or "testing"; it may have looked OK on
> their model XYZ word-processor but completely screwy to _everyone_ who
> receives it.

Fair enough.  This is hardly causing me lost sleep, nor is it anywhere
near the most important thing I wish Gnus did better.

> I note that you sent it in UTF-8; was that the coding system used in the
> original spam?

Nope.

| MIME-Version: 1.0
| Content-Type: text/plain; charset="ISO-2022-JP"
| Content-Transfer-Encoding: 7bit

I can try to extract the original text and send it along uuencoded or
something, but in view of what you say above, I'm not sure it's worth
bothering...?

zw



  reply	other threads:[~2005-02-23  3:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-22  6:03 Zack Weinberg
2005-02-22  8:56 ` Daniel Pittman
2005-02-23  0:28   ` Miles Bader
2005-02-23  2:04     ` Katsumi Yamaoka
2005-02-22  9:38 ` Reiner Steib
2005-02-22 23:57 ` Miles Bader
2005-02-23  3:15   ` Zack Weinberg [this message]
2005-02-23  8:18 ` Henrik Enberg
2005-02-23  8:34   ` Zack Weinberg
2005-02-23 15:14     ` Adam Duck
2005-02-24  0:50       ` Miles Bader

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=87d5usj7ar.fsf@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=ding@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).