From: Kenichi Handa <handa@m17n.org>
Cc: vincent@vinc17.org, romain@orebokech.com, walters@gnu.org,
emacs-devel@gnu.org
Subject: Re: Should `auto-coding-functions' be mode-specific?
Date: Thu, 04 Jan 2007 13:14:23 +0900 [thread overview]
Message-ID: <E1H2Jzj-000089-2O@etlken.m17n.org> (raw)
In-Reply-To: <E1H2IOA-0002Wy-NM@fencepost.gnu.org> (message from Richard Stallman on Wed, 03 Jan 2007 21:31:30 -0500)
In article <E1H2IOA-0002Wy-NM@fencepost.gnu.org>, Richard Stallman <rms@gnu.org> writes:
> This explains the problem. But anyway, there was some text before
> the HTML code, meaning that the HTML code was included in some text
> file. So, in this case, I don't think taking the charset from the
> META header is a correct behavior.
> That criterion is perhaps feasible to implement.
> Handa, what do you think?
Perhaps. Currently sgml-xml-auto-coding-function and
sgml-html-meta-auto-coding-function are registred in
auto-coding-functions.
And sgml-xml-auto-coding-function checks whether the buffer
is XML or not. So, sgml-html-meta-auto-coding-function
should do the similar check too. Someone who knows the
syntax of HTML well, please fix the function.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2007-01-04 4:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 20:43 Should `auto-coding-functions' be mode-specific? Romain Francoise
2007-01-02 22:14 ` Lennart Borgman (gmail)
2007-01-03 0:54 ` Kevin Ryde
2007-01-03 3:34 ` Richard Stallman
2007-01-03 12:09 ` Vincent Lefevre
2007-01-04 2:31 ` Richard Stallman
2007-01-04 4:14 ` Kenichi Handa [this message]
2007-01-04 19:02 ` Romain Francoise
2007-01-04 22:33 ` Richard Stallman
2007-01-05 18:04 ` Romain Francoise
2007-01-03 5:26 ` Kevin Rodgers
2007-01-03 14:18 ` Ralf Mattes
2007-01-04 8:44 ` Romain Francoise
2007-01-06 23:33 ` Juri Linkov
2007-01-07 13:47 ` Romain Francoise
2007-01-07 16:22 ` Juri Linkov
2007-01-08 19:46 ` Romain Francoise
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=E1H2Jzj-000089-2O@etlken.m17n.org \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=romain@orebokech.com \
--cc=vincent@vinc17.org \
--cc=walters@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 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.