From: Laura Conrad <lconrad@world.std.com>
Cc: ding@gnus.org
Subject: Re: decoding characters
Date: 12 May 2000 10:38:45 -0400 [thread overview]
Message-ID: <kh766sjrfyi.fsf@acme47.nineco.com> (raw)
In-Reply-To: Toby Speight's message of "12 May 2000 11:34:46 +0100"
>>>>> "Toby" == Toby Speight <streapadair@gmx.net> writes:
Laura> Laura Conrad <URL:mailto:lconrad@world.std.com>
0> In article <kh7og6crir4.fsf@acme47.nineco.com>, Laura wrote:
Laura> I got an email which contained a table of TeX codings for
Laura> characters, and also the characters. Most of them looked like
Laura> I expected, but there were 3 that displayed wrong in my gnus:
Laura>
Laura> \oe (displayed as \234)
Laura> \OE (displayed as \214)
Laura> \"Y (displayed as \237)
Laura>
Laura> I'm using: xemacs*font:
Laura> -etl-fixed-medium-r-normal--16-160-72-72-c-80-iso8859-1
Toby> Is your Emacs unibyte or multibyte?
How do I tell? It's whatever came with RedHat.
Laura> When I just 'more' the mail file in and xterm, \oe and \OE are
Laura> blank, but \"y displays fine, using the same font as I have
Laura> defined for xemacs.
Toby> I think the ETL fonts include \"Y at \237 - but you haven't told this
Toby> to Emacs. (aset standard-display-table ?\237 [?\237])
This gives me
Wrong type argument: arrayp, nil
Toby> Actually, that's not the most relevant header. What would be more
Toby> useful would be the Content-Type line of the particular part you're
Toby> having problems with.
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
--
Laura (mailto:lconrad@world.std.com , http://www.world.std.com/~lconrad/ )
(617) 661-8097 fax: (801) 365-6574
233 Broadway, Cambridge, MA 02139
next prev parent reply other threads:[~2000-05-12 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-11 19:26 Laura Conrad
2000-05-12 7:19 ` Roland Mas
2000-05-12 10:34 ` Toby Speight
2000-05-12 14:38 ` Laura Conrad [this message]
2000-05-12 15:22 ` Toby Speight
2000-05-12 15:39 ` Toby Speight
2000-05-14 18:11 ` Mike Fabian
2000-05-15 14:34 ` Laura Conrad
2000-05-15 14:56 ` Kai Großjohann
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=kh766sjrfyi.fsf@acme47.nineco.com \
--to=lconrad@world.std.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).