unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Default coding system ?
Date: Thu, 04 Dec 2003 20:10:43 +0100	[thread overview]
Message-ID: <m3smk0s8jw.fsf@defun.localdomain> (raw)
In-Reply-To: mailman.980.1070473405.399.help-gnu-emacs@gnu.org

"Eli Zaretskii" <eliz@elta.co.il> writes:

> François Fleuret writes:
>
>> I read my mail with gnus, and from time to time, especially with spam
>> mails, gnus asks for a coding system with the following warning

You could try Gnus 5.10.  There has been quite a lot of changes in
this area since 5.9.

>> And this coding system issue is such a mess that I can not find the
>> courage to go deeper in the documentations.
>
> Why do you need courage to read the documentation?  The manual doesn't
> bite, you know.  So please do try reading it, and if something there
> isn't clear, please complain on gnu.emacs.bug about documentation
> quality.

I agree with François that it's a mess.  It don't really blame the
documentation -- it's more the design that's hard to understand and
use, i.e. the multibyte vs. unibyte distinction and character-set
vs. coding-system vs. mime-charset.

Also, stuff like CCL and MULE isn't particularly well documented.

  parent reply	other threads:[~2003-12-04 19:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 12:22 Default coding system ? François Fleuret
2003-12-03 14:14 ` Joakim Hove
2003-12-03 16:38 ` Eli Zaretskii
     [not found] ` <mailman.980.1070473405.399.help-gnu-emacs@gnu.org>
2003-12-04 19:10   ` Jesper Harder [this message]
2003-12-05 15:43     ` Eli Zaretskii
     [not found]     ` <mailman.1196.1070642811.399.help-gnu-emacs@gnu.org>
2003-12-05 17:08       ` Jesper Harder
2003-12-17 20:48         ` Kai Grossjohann
2003-12-05 16:35   ` François Fleuret
2003-12-06  8:50     ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3smk0s8jw.fsf@defun.localdomain \
    --to=harder@myrealbox.com \
    /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).