From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Lots of sets.
Date: 04 Dec 1998 01:57:07 +0100 [thread overview]
Message-ID: <m3btlkyba4.fsf@sparky.gnus.org> (raw)
In-Reply-To: Michael Welsh Duggan's message of "Thu, 03 Dec 1998 14:49:21 GMT"
Michael Welsh Duggan <md5i@cs.cmu.edu> writes:
> Amharic: broken. I could see the escape codes rather then the characters.
> Lao: Partially broken. Some visible escape sequences.
> Tigrigna: Same as Amharic.
These are all, er, weird coding systems. Or, at least, they use weird
MULE charsets -- `composition'. What *is* that?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-12-04 0:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-02 23:35 Lars Magne Ingebrigtsen
1998-12-02 23:48 ` Hrvoje Niksic
1998-12-03 8:03 ` Yair Friedman
1998-12-03 12:11 ` Lars Magne Ingebrigtsen
1998-12-03 13:38 ` Yair Friedman
1998-12-03 14:49 ` Michael Welsh Duggan
1998-12-04 0:57 ` Lars Magne Ingebrigtsen [this message]
1998-12-04 5:12 ` Michael Welsh Duggan
1998-12-03 21:01 ` Jack Vinson
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=m3btlkyba4.fsf@sparky.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).