unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Coding systems documentation
Date: Mon, 01 Dec 2008 10:30:49 +0900	[thread overview]
Message-ID: <E1L6xcf-0005Fl-8v@etlken.m17n.org> (raw)
In-Reply-To: <uoczwlx0q.fsf@gnu.org> (message from Eli Zaretskii on Sun, 30 Nov 2008 23:33:09 +0200)

In article <uoczwlx0q.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

> > From: Richard M Stallman <rms@gnu.org>
> > Date: Sun, 30 Nov 2008 11:43:56 -0500
> > 
> >     +@c I think this paragraph is no longer correct.
> >     +@ignore
> >        Most coding systems specify a particular character code for
> >      conversion, but some of them leave the choice unspecified---to be chosen
> >      heuristically for each file, based on the data.
> >     +@end ignore
> > 
> > I think these still exist.  For example, there are `undecided' and friends.

> Is this only about undecided? or are there other examples?

All coding systems that don't have -unix, -dos, and -mac at
the tail leaves the choice of eol-format unspecified.  But,
if you are going to mention about eol-format at the
different place, yes, `undecided' is the only coding that
doesn't specify how text is encode.

> If it's only about undecided, I'd like to rewrite this text to speak
> explicitly about undecided.  Then it won't sound so mysteriously.

It seems to be a good idea.

By the way, "specify a particular character code for
conversion" is a little bit strange.  "specify a particular
conversion rule between an encoded byte sequence and a
character sequence." is more accurate (and I think clearer).

---
Kenichi Handa
handa@ni.aist.go.jp




  reply	other threads:[~2008-12-01  1:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-30 16:43 Coding systems documentation Richard M Stallman
2008-11-30 21:33 ` Eli Zaretskii
2008-12-01  1:30   ` Kenichi Handa [this message]
2008-12-01  4:11     ` Eli Zaretskii
2008-12-01  5:22       ` Kenichi Handa
2008-12-01 14:06   ` Richard M Stallman

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=E1L6xcf-0005Fl-8v@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).