unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: 13936@debbugs.gnu.org, Kenichi Handa <handa@gnu.org>
Subject: bug#13936: Default to UTF-8 for most Emacs source files
Date: Mon, 18 Mar 2013 13:40:10 -0700	[thread overview]
Message-ID: <51477BAA.6020601@cs.ucla.edu> (raw)
In-Reply-To: <jwv7gl496wf.fsf-monnier+emacs@gnu.org>

Another thought is to add support for a local variable 'lang'
to specify the language, HTML-style, e.g.:

;; Local Variables:
;; coding: utf-8
;; lang: ja
;; End:

where the "ja" comes from the usual standard list (see Internet BCP 47
and <http://www.iana.org/assignments/language-subtag-registry>).
Emacs could use the language to set charset-priority on a per-file basis.
This would be friendlier to users than the
"eval: (set-charset-priority 'japanese-jisx0208)" approach
that I mentioned earlier.  But it'd be more implementation work.

In the meantime I will propose a stripped-down patch that does not
alter TUTORIAL.ja and the other CJK files; this should avoid the
charset problems that Mr. Handa mentioned.





  reply	other threads:[~2013-03-18 20:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 21:16 bug#13936: Default to UTF-8 for most Emacs source files Paul Eggert
2013-03-12 21:54 ` Eli Zaretskii
2013-03-12 22:04 ` Andreas Schwab
2013-03-13  0:01   ` Paul Eggert
2013-03-14  3:48   ` handa
2013-03-18  7:22     ` Paul Eggert
2013-03-18  9:43       ` Andreas Schwab
2013-03-18 13:27         ` Stefan Monnier
2013-03-18 20:40           ` Paul Eggert [this message]
2013-03-20  8:18             ` Kenichi Handa
2013-03-20 16:43               ` Paul Eggert
2013-03-20 16:48               ` Paul Eggert
2013-04-02  1:20               ` Paul Eggert
2013-04-03 18:31                 ` Stefan Monnier
2013-04-03 18:39                   ` Eli Zaretskii
2013-04-04  0:35                     ` Stefan Monnier
2013-04-05 15:03                       ` Kenichi Handa
2013-04-05 18:58                         ` Stefan Monnier
2013-03-18 20:44           ` Paul Eggert

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=51477BAA.6020601@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=13936@debbugs.gnu.org \
    --cc=handa@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).