Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: "Coding system"?  Eh?
Date: 05 Sep 1998 23:47:33 +0200	[thread overview]
Message-ID: <kigu32m8c5m.fsf@jagor.srce.hr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "05 Sep 1998 23:12:01 +0200"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Hrvoje Niksic <hniksic@srce.hr> writes:
> 
> > I believe Michael's point was that, under Mule, you can create
> > coding systems that have nothing to do with character sets, such
> > as a `gzip' coding-system.
> 
> They do that?  And if the unzipped file results in something that's
> iso-2022-jp, do they run it though the decoding twice, or do they
> have a gzip-iso-2022-jp coding system, as Morioka almost suggested
> for base64?  (base64-iso-2022-jp, etc.)  The latter would be a
> nightmare, and the former would be just yucky.

I believe XEmacs/Mule allows you to create coding-system chains (at
least I seem to recall seing internal code to that effect), the yucky
solution, whereas in FSF Emacs you get the nightmare one.

> > Coding systems are Emacs-specific hybrids between character sets
> > and their external representation.  This probably makes them
> > different enough from "character sets" to warrant for a separate
> > name.
> 
> Hm.  I did a `M-x list-coding-systems', and it listed nothing but
> character sets.

Well, I never said all of this was implemented.  :-)  I was trying to
explain the concept, the way I see it.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Ask not for whom the <CONTROL-G> tolls.


  reply	other threads:[~1998-09-05 21:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-09-05 16:01 Lars Magne Ingebrigtsen
1998-09-05 16:31 ` Michael Welsh Duggan
1998-09-05 20:07   ` Lars Magne Ingebrigtsen
1998-09-05 20:45     ` Hrvoje Niksic
1998-09-05 21:12       ` Lars Magne Ingebrigtsen
1998-09-05 21:47         ` Hrvoje Niksic [this message]
1998-09-07 15:12     ` David Kågedal
1998-09-09 18:50       ` François Pinard
1998-09-10 12:45         ` David Kågedal
1998-09-10 20:21           ` Gisle Aas
1998-09-11  6:27             ` François Pinard
1998-09-11  6:16           ` François Pinard
1998-09-11 16:14         ` Hallvard B Furuseth
2002-10-20 23:13       ` Lars Magne Ingebrigtsen
1998-09-09 18:59         ` François Pinard

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=kigu32m8c5m.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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).