Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Subject: Re: CT: text/plain; charset=us-ascii, CTE: 8bit
Date: 28 Oct 1998 19:38:23 +0000	[thread overview]
Message-ID: <rzqlnm0pjdc.fsf@djlvig.dl.ac.uk> (raw)
In-Reply-To: Hrvoje Niksic's message of "Tue, 27 Oct 1998 20:08:26 GMT"

>>>>> "HN" == Hrvoje Niksic <hniksic@srce.hr> writes:

 HN> `read-coding-system' is the workhorse behind `(interactive "z")',
 HN> FWIW.

But coding systems aren't charsets, of course.  OTOH, how are you
supposed to MIME multiple MULE charsets in a region anyway?  Is the
buffer's coding system (for write?) actually the relevant thing?

BTW, has the doc for `coding-system-get' been noticed in this
connexion?

 - Function: coding-system-get CODING-SYSTEM PROPERTY
     This function returns the specified property of the coding system
     CODING-SYSTEM.  Most coding system properties exist for internal
     purposes, but one that you might find useful is `mime-charset'.
     That property's value is the name used in MIME for the character
     coding which this coding system can read and write.  Examples:

          (coding-system-get 'iso-latin-1 'mime-charset)
               => iso-8859-1
          (coding-system-get 'iso-2022-cn 'mime-charset)
               => iso-2022-cn
          (coding-system-get 'cyrillic-koi8 'mime-charset)
               => koi8-r

     The value of the `mime-charset' property is also defined as an
     alias for the coding system.

-- 
MULE's Upping Lars's Exasperation?


  reply	other threads:[~1998-10-28 19:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-25 19:53 Bjørn Mork
1998-10-25 22:38 ` Lars Magne Ingebrigtsen
1998-10-26 19:17   ` Dave Love
1998-10-26 21:31     ` Lars Magne Ingebrigtsen
1998-10-27 18:50       ` Dave Love
1998-10-27 20:06         ` Hrvoje Niksic
1998-10-28 19:38           ` Dave Love [this message]
1998-11-07 17:07             ` Lars Magne Ingebrigtsen

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=rzqlnm0pjdc.fsf@djlvig.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    /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).