From: Richard M Stallman <rms@gnu.org>
To: emacs-devel@gnu.org
Subject: Coding systems documentation
Date: Sun, 30 Nov 2008 11:43:56 -0500 [thread overview]
Message-ID: <E1L6pOm-0005NQ-IU@fencepost.gnu.org> (raw)
+@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.
next reply other threads:[~2008-11-30 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 16:43 Richard M Stallman [this message]
2008-11-30 21:33 ` Coding systems documentation Eli Zaretskii
2008-12-01 1:30 ` Kenichi Handa
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=E1L6pOm-0005NQ-IU@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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).