From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: list guidelines
Date: Fri, 26 Jan 2001 11:55:30 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.21.0101261148300.5743-100000@ignatious> (raw)
In-Reply-To: <Pine.LNX.4.31.0101261026360.949-100000@atidenauth.den.wantweb.net>
On Fri, 26 Jan 2001 raul@asmodean.net wrote:
> Yours is one of those that comes up with the wrong character set. So this
> means that since you are using outlook express you are either sending html
> or rich text messages.
While he is using Outlook Express ver 5.5 he is NOT sending html or rich
text. In fact, for the record, if you are not using the same character
set, you are most likely the person who is non-compliant with RFC
standards. Chances are you are using an older version of Pine.
I am using the same chacter set. And it is the default. But I have a
fairly recent version of Pine. Pine was first written before extended
character sets were common. But with the internationalization of the
internet the need for characters outside our precious English language
were needed. This gave rise to the extended character sets. In essense it
starts with plain ascii and adds charcters needed (or desired) for a given
region. These also coincide with the country code pages if you have seen
some settings for that.
Again, if you are recieving the message regularly you are probably the one
who is NOT folling the RFC on the subject (sorry but the exact number
exscapes me right now). You (probably) can change this. If you can't you
really should consider upgrading your version of Pine. There are other
neat features that have been added as well.
=======
Kirk Wood
Cpt.Kirk@1tree.net
Cluelessness
There are no stupid questions, but there are a lot of
inquisitive idiots
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Spivey
` David Poehlman
` raul
` Kirk Wood [this message]
` Chris Nestrud
` raul
` Geoff Shang
` raul
` Kirk Wood
` Geoff Shang
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=Pine.LNX.4.21.0101261148300.5743-100000@ignatious \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).