all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Werner LEMBERG <wl@gnu.org>
To: eliz@gnu.org
Cc: stephen@xemacs.org, handa@m17n.org, emacs-devel@gnu.org
Subject: Re: per-buffer language environments
Date: Sat, 18 Dec 2010 07:29:37 +0100 (CET)	[thread overview]
Message-ID: <20101218.072937.305030077.wl@gnu.org> (raw)
In-Reply-To: <8362ushb1c.fsf@gnu.org>


>   . There's any number of possible use-cases for needing this kind
>     of feature.  They are all quite rare (if they weren't, we would
>     have many complaints about not having such a feature, which we
>     don't).

I would rather say that these use-cases are all quite new.
Previously, Emacs didn't do too well with Unicode, and only recently
free CJK fonts (especially for Japanese) are available as TrueType
fonts so that the user has a choice to select between well-crafted
fonts.

>     The current heuristics encoded in the global language environment
>     does not cover well rare and marginal use-cases, being just that
>     -- a set of heuristics.  It is therefore quite probable that just
>     making the language environment buffer-local and keeping all the
>     rest of its machinery and semantics would do the wrong thing for a
>     large portion of the use-cases which need such a buffer-local
>     feature.

I don't think so, however, people on this list should submit more
use-cases if possible so that we can decide this issue easier.

>     Setting the language can surely identify a small set of
>     appropriate encodings, but I very much doubt that it can
>     correctly select The Right One.

Note that I'm specifically talking about Unicode.  IMHO, handling of
all other encodings should stay as-is since they will be extinct soon
anyway.


    Werner



  reply	other threads:[~2010-12-18  6:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-11 15:25 per-buffer language environments Werner LEMBERG
2010-12-11 19:00 ` Eli Zaretskii
2010-12-12  6:25   ` Werner LEMBERG
2010-12-13  7:56     ` Kenichi Handa
2010-12-13  9:27       ` Werner LEMBERG
2010-12-13 10:59         ` Kenichi Handa
2010-12-13 12:15           ` Werner LEMBERG
2010-12-13 11:47       ` Eli Zaretskii
2010-12-14 11:38         ` Stephen J. Turnbull
2010-12-14 15:14           ` Eli Zaretskii
2010-12-15  4:51             ` Stephen J. Turnbull
2010-12-15  6:47               ` Eli Zaretskii
2010-12-15  7:45                 ` Werner LEMBERG
2010-12-16 21:10                 ` Stephen J. Turnbull
2010-12-17 11:51                   ` Eli Zaretskii
2010-12-18  6:29                     ` Werner LEMBERG [this message]
2010-12-18  9:30                     ` Stephen J. Turnbull
2010-12-21 18:39                       ` Eli Zaretskii
2010-12-21 21:16                       ` Werner LEMBERG
2010-12-22  6:52                         ` Stephen J. Turnbull
2010-12-22  7:42                           ` Werner LEMBERG
2010-12-17  0:51                 ` Kenichi Handa
2010-12-17  2:48                   ` Stephen J. Turnbull
2010-12-17 11:05                   ` Eli Zaretskii
2010-12-18 17:03       ` Per Starbäck
2010-12-19 13:54         ` Stefan Monnier
2010-12-19 21:05           ` Dimitri Fontaine

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101218.072937.305030077.wl@gnu.org \
    --to=wl@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=stephen@xemacs.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.