From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: coding tags and utf-16
Date: Wed, 04 Jan 2006 22:46:13 -0500 [thread overview]
Message-ID: <E1EuM4r-00051L-Sf@fencepost.gnu.org> (raw)
In-Reply-To: <E1Eu2Ln-00032e-00@etlken> (message from Kenichi Handa on Wed, 04 Jan 2006 15:42:23 +0900)
If a file is encoded without BOM, we must use the less
reliable heuristics to guess utf-16be or utf-16le. If you
find a coding-tag spec by ignoring all zero bytes at even
byte indexes, it means that the file is, in high
possibility, utf-16be whatever the tag value is. If you
find a coding-tag spec by ignoring all zero bytes at odd
byte indexes, it means that the file is utf-16le whatever
the tag value is.
Does Emacs already implement these heuristics?
But, those are anyway just heuristics; not 100% reliable.
So I think we need a user option to turn it on and off, or
perhaps a user option to select which kind of heuristics.
Should we install this option now?
next prev parent reply other threads:[~2006-01-05 3:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 8:00 coding tags and utf-16 Werner LEMBERG
2005-12-23 23:43 ` Werner LEMBERG
2005-12-24 16:32 ` Richard M. Stallman
2006-01-04 6:42 ` Kenichi Handa
2006-01-04 14:58 ` Werner LEMBERG
2006-01-05 3:46 ` Richard M. Stallman [this message]
2006-01-05 4:33 ` Kenichi Handa
2006-01-05 12:24 ` David Kastrup
2006-01-06 0:27 ` Andreas Schwab
2006-01-05 23:11 ` Richard M. Stallman
2006-01-06 1:22 ` Werner LEMBERG
2006-01-06 11:26 ` Kenichi Handa
2006-01-07 4:23 ` Richard M. Stallman
2006-01-07 6:05 ` Kenichi Handa
2006-01-05 15:56 ` Stefan Monnier
2006-01-06 6:31 ` Kenichi Handa
2006-01-06 10:28 ` David Kastrup
2006-02-09 0:32 ` Kevin Rodgers
2006-02-28 1:08 ` Kenichi Handa
2006-03-04 20:34 ` Benjamin Riefenstahl
2006-03-06 13:04 ` Kenichi Handa
2006-03-06 19:35 ` Benjamin Riefenstahl
2006-03-07 1:02 ` Kenichi Handa
2006-03-08 5:42 ` Tomas Zerolo
2006-03-16 2:23 ` Kenichi Handa
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=E1EuM4r-00051L-Sf@fencepost.gnu.org \
--to=rms@gnu.org \
--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).