unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, emacs-devel@gnu.org
Subject: Re: lisp/ChangeLog coding system
Date: Sun, 28 Apr 2002 21:55:29 -0400	[thread overview]
Message-ID: <200204290155.g3T1tT814296@rum.cs.yale.edu> (raw)
In-Reply-To: 87znzn48el.fsf@tleepslib.sk.tsukuba.ac.jp

> One aspect is making better guesses about desired coding systems.

I'm not sure what kind of improvements you're thinking about.

> Another is getting the trash coding systems out of the prompt to the user.

I agree that the more "esoteric" systems should be made less
visible.  They are already pushed to the end of the list, but
the list is long (because it always includes the "catch-all"
systems like emacs-mule, iso-2022 and iso8859-with-esc) and looks
just very confusing.  We should probably try to split it into
"likely" and "unlikely" options.  Where the cut-off point should be,
I don't know (non-MIME coding-systems should be in the "unlikely"
list, tho).

>  Eg, I doubt most users _ever_ want to use the -with-esc coding
> systems.  (As far as I can tell X Compound Text should serve the
> purpose fine, and users can tell for sure that they don't know what it
> does.  The ISO-8859-with-esc are tempting for naive users as "the
> closest to what I want").

I don't even know why those systems exist.

> A sample implementation of these aspects (for XEmacs only) is latin-unity:

I'm not sure in which sense this is related.

> The two big problems with this package (to the author's mind ;-) are
> that it doesn't handle anything but ISO Latin yet, and it doesn't work
> on GNU Emacs.  The beta testers seem happy with the functionality.
> The UI needs tuning, of course.

Looking at the README, I have the impression that most of the functionality
is already part of the Emacs CVS code (mostly thanks to Dave's
ucs-tables.el).  Someone should try and figure out the details.


	Stefan

  reply	other threads:[~2002-04-29  1:55 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 14:45 lisp/ChangeLog coding system Gerd Moellmann
2002-04-27 22:41 ` Richard Stallman
2002-04-27 23:05   ` Michael Kifer
2002-04-29  5:01     ` Eli Zaretskii
2002-04-29 11:22       ` Gerd Moellmann
2002-04-29 13:33         ` Eli Zaretskii
2002-04-30  5:18           ` Richard Stallman
2002-04-30  5:31             ` Eli Zaretskii
2002-05-01  7:13               ` Richard Stallman
2002-05-01 11:56                 ` Eli Zaretskii
2002-04-29  5:06     ` Richard Stallman
2002-04-29  6:10       ` Michael Kifer
2002-04-29 10:00         ` Eli Zaretskii
2002-04-30  5:18           ` Richard Stallman
2002-04-30  5:19         ` Richard Stallman
2002-04-30  5:22           ` Michael Kifer
2002-04-30  5:32             ` Eli Zaretskii
2002-04-30  5:53               ` Michael Kifer
2002-04-30  9:19                 ` Eli Zaretskii
2002-04-30 15:35                   ` Michael Kifer
2002-04-28  3:06   ` Karl Eichwalder
2002-04-28 18:22     ` Eli Zaretskii
2002-04-28 23:19       ` Stefan Monnier
2002-04-29  5:03         ` Eli Zaretskii
2002-04-29 18:39         ` Richard Stallman
2002-04-29  1:10       ` Stephen J. Turnbull
2002-04-29  1:55         ` Stefan Monnier [this message]
2002-04-29  5:07           ` Eli Zaretskii
2002-04-29 11:28           ` Stephen J. Turnbull
2002-04-29 11:49             ` Miles Bader
2002-04-29 13:31             ` Stefan Monnier
2002-04-29 15:54               ` Stephen J. Turnbull
2002-04-29 15:56               ` Karl Eichwalder
2002-04-29 16:38               ` Miles Bader
2002-04-29 13:43             ` Eli Zaretskii
2002-04-29  5:05     ` Richard Stallman
2002-04-29 15:52       ` Karl Eichwalder
2002-04-29 16:37         ` Stefan Monnier
2002-04-29 18:43           ` Eli Zaretskii
2002-04-29 18:41         ` Eli Zaretskii
2002-04-29 19:12           ` Simon Josefsson
2002-04-30  4:35             ` Eli Zaretskii
2002-04-30  8:50               ` Simon Josefsson
2002-04-30  5:19         ` Richard Stallman
2002-04-30 18:09           ` Karl Eichwalder

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=200204290155.g3T1tT814296@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=eliz@is.elta.co.il \
    --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).