From: Richard Stallman <rms@gnu.org>
Cc: handa@m17n.org, emacs-devel@gnu.org, monnier@IRO.UMontreal.CA,
jasonr@f2s.com, pogonyshev@gmx.net
Subject: Re: windows-1251 language environment
Date: Wed, 22 Oct 2003 05:24:32 -0400 [thread overview]
Message-ID: <E1ACFEG-0004ZT-Op@fencepost.gnu.org> (raw)
In-Reply-To: <rzq1xt7r8m9.fsf@albion.dl.ac.uk> (message from Dave Love on Mon, 20 Oct 2003 20:50:54 +0100)
They appear to say that the components of the name are
standardized, but the Single Unix Spec v3 (now equivalent to POSIX?)
actually says they are implementation-defined:
POSIX has never tried to specify the locales. But if there is a
broadly accepted de-facto standard, that's just as good for us to use
as an official standard.
> What I said is that Emacs
> should not *rely on* an external mechanism such as locales for
> customization. It should provide an Emacs-natural customize mechanism
> *also*.
I don't think customization based on language, territory and codeset
is really unnatural.
1. You specify the locale with an envvar. Emacs must provide
a way to do it with commands or user options.
2. It is ok to have a command or user option whose argument or value
is a locale name. But there should also be a command or user option
where you specify just the language, and other things default from
that to the extent possible. And that's what should be in the menus.
next prev parent reply other threads:[~2003-10-22 9:24 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.878.1064866468.21628.bug-gnu-emacs@gnu.org>
[not found] ` <200310032356.54476.pogonyshev@gmx.net>
[not found] ` <rzq1xtrsdrm.fsf@albion.dl.ac.uk>
[not found] ` <200310060013.52049.pogonyshev@gmx.net>
2003-10-07 2:54 ` windows-1251 language environment Kenichi Handa
2003-10-07 11:56 ` Anton Zinoviev
2003-10-12 15:45 ` Dave Love
2003-10-17 12:49 ` Anton Zinoviev
2003-10-17 13:22 ` Terje Rosten
2003-10-17 14:36 ` Anton Zinoviev
2003-10-17 16:58 ` Terje Rosten
2003-10-21 22:38 ` Dave Love
2003-10-23 9:23 ` Richard Stallman
2003-10-24 17:07 ` Anton Zinoviev
2003-10-08 4:51 ` Richard Stallman
2003-10-08 10:40 ` Kenichi Handa
2003-10-09 14:44 ` Richard Stallman
2003-10-12 15:40 ` Dave Love
2003-10-13 23:50 ` Kenichi Handa
2003-10-14 19:31 ` Richard Stallman
2003-10-15 13:44 ` Kenichi Handa
2003-10-15 14:55 ` Stefan Monnier
2003-10-16 9:16 ` Stephen J. Turnbull
2003-10-16 16:44 ` Stefan Monnier
2003-10-17 6:10 ` Stephen J. Turnbull
2003-10-21 22:48 ` Dave Love
2003-10-20 19:47 ` Dave Love
2003-10-16 14:06 ` Richard Stallman
2003-10-28 8:51 ` Kenichi Handa
2003-10-10 17:11 ` Dave Love
2003-10-10 17:42 ` Stefan Monnier
2003-10-12 17:21 ` Richard Stallman
2003-10-14 22:24 ` Dave Love
2003-10-15 20:00 ` Richard Stallman
2003-10-20 19:50 ` Dave Love
2003-10-22 9:24 ` Richard Stallman [this message]
2003-10-25 16:10 ` Dave Love
2003-10-26 15:33 ` Alex Schroeder
2003-10-28 8:50 ` Kenichi Handa
2003-10-27 7:02 ` Richard Stallman
2003-10-28 12:35 ` Dave Love
2003-10-29 19:01 ` Richard Stallman
2003-10-15 22:27 ` Jason Rumney
2003-10-16 16:16 ` Kevin Rodgers
2003-10-16 16:38 ` Jason Rumney
2003-10-14 0:44 ` Kenichi Handa
2003-10-14 19:31 ` Richard Stallman
2003-10-14 22:33 ` Dave Love
2003-10-13 12:46 ` Dave Love
2003-10-14 0:37 ` Kenichi Handa
2003-10-15 14:38 ` Dave Love
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=E1ACFEG-0004ZT-Op@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
--cc=jasonr@f2s.com \
--cc=monnier@IRO.UMontreal.CA \
--cc=pogonyshev@gmx.net \
/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).