From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
Cc: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
Eli Zaretskii <eliz@is.elta.co.il>,
emacs-devel@gnu.org
Subject: Re: lisp/ChangeLog coding system
Date: Mon, 29 Apr 2002 09:31:18 -0400 [thread overview]
Message-ID: <200204291331.g3TDVJX19627@rum.cs.yale.edu> (raw)
In-Reply-To: 87it6a3frc.fsf@tleepslib.sk.tsukuba.ac.jp
> >>>>> "Stefan" == Stefan Monnier <monnier+gnu/emacs@rum.cs.yale.edu> writes:
>
> >> One aspect is making better guesses about desired coding
> >> systems.
>
> Stefan> I'm not sure what kind of improvements you're thinking
> Stefan> about.
>
> Well, in the version (mid-January, maybe?) of GNU Emacs I have, when I
> tried saving a buffer with mixed ascii, latin-1, and latin-2 in it, it
> gave me an abominably long list of coding systems including mule
> internal, all the -with-esc systems, and iso-2022-jp-2. But all of
> the characters used in the buffer are in ISO-8859-2, it's just Mule
> making false distinctions.
>
> At the very least, the defaults in Emacs should be to identify
> identical characters (eg, those from the Latin-## subsets) and to
> distinguish those where unification is controversial (the Han
> ideographs).
As Miles said, you can call (ucs-unify-8859 t) to unify the latin
charsets when saving a file. Better yet: you don't need to do it any
more because it's now the default behavior.
> Stefan> non-MIME coding-systems should be in the "unlikely" list, tho.
>
> There is no unique "the unlikely list".
>
> For example, if I were Croatian, I probably would want the buffer
> described above saved in ISO-8859-2 without being asked,
That's what happens right now.
> but a German
> would probably want to save it in UTF-8 (or maybe ISO-2022-7 if she
> were an Emacs developer), or be queried, defaulting to ISO-8859-2.
A German would get a prompt where iso-8859-2 and utf-8 should
be near the beginning of the list of coding-systems she can
choose from.
> And what's a "non-MIME coding system"?
I don't know. All I know is that it's used when sorting coding-systems
so that the list has more "likely" coding systems at the beginning.
I think it's also used to choose more user-friendly names when a coding-system
has several aliases (such as mule-utf-8 and utf-8. Don't ask me why the
coding-system is called `mule-utf-8' and why `utf-8' is only an alias, tho).
> As for most functionality being in Emacs, yes, that's why I said I'd
> help refactor; relative to ucs-tables.el the contribution is all UI.
> My duplication[1] of ucs-tables is straightforward, not terribly
> efficient code; all the meat is devoted to the question of "how do we
> know which coding systems to offer the user". Specifically I address
> the issues of preferred unibyte systems and preferred universal
> systems described above.
I'm beginning to understand, thank you,
Stefan
next prev parent reply other threads:[~2002-04-29 13:31 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
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 [this message]
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=200204291331.g3TDVJX19627@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).