From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: emacs-devel@gnu.org
Subject: Re: utf-16le vs utf-16-le
Date: Mon, 14 Apr 2008 21:46:18 +0300 [thread overview]
Message-ID: <uskxoqnph.fsf@gnu.org> (raw)
In-Reply-To: <87lk3gfg40.fsf@uwakimon.sk.tsukuba.ac.jp>
> From: "Stephen J. Turnbull" <stephen@xemacs.org>
> Date: Tue, 15 Apr 2008 03:25:51 +0900
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>
> I agree, as you state it, it's obvious. My question is "why does that
> need to be part of the coding system?"
Well, consistency with other ``add-ons'', such as EOL format, is one
reason.
> At present the UTF-16 and
> UTF-32 Unicode coding systems (in the abstract) have *twenty-seven*
> variants each (BOM-required, BOM-prohibited, BOM-autodetected X be,
> le, system-dependent X CR, LF, CRLF), and UTF-8 needs *nine*.
Which 9 are needed by UTF-8? I only see 4: the auto-detecting one,
then one each for -unix. -dos, and -mac. What am I missing?
> What I proposed was a more generic concept where use of signatures and
> the EOL convention would (at least to the user) appear as buffer-local
> variables.
Don't forget that en/decoding is used on strings as well, not only on
buffers. Buffer-local variables won't cut it, I think.
next prev parent reply other threads:[~2008-04-14 18:46 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 14:54 utf-16le vs utf-16-le Eli Zaretskii
2008-04-13 19:32 ` Stefan Monnier
2008-04-14 5:17 ` Kenichi Handa
2008-04-14 6:10 ` David Kastrup
2008-04-14 18:54 ` Eli Zaretskii
2008-04-14 19:04 ` David Kastrup
2008-04-14 17:38 ` Eli Zaretskii
2008-04-14 18:57 ` Eli Zaretskii
2008-04-13 22:23 ` Stephen J. Turnbull
2008-04-14 3:19 ` Eli Zaretskii
2008-04-14 7:32 ` Stephen J. Turnbull
2008-04-14 8:20 ` David Kastrup
2008-04-14 18:25 ` Stephen J. Turnbull
2008-04-14 18:46 ` Eli Zaretskii [this message]
2008-04-14 21:01 ` Stephen J. Turnbull
2008-04-14 21:15 ` Andreas Schwab
2008-04-15 0:22 ` Stephen J. Turnbull
2008-04-15 3:25 ` Eli Zaretskii
2008-04-15 16:51 ` Stephen J. Turnbull
2008-04-15 20:09 ` Eli Zaretskii
2008-04-15 20:31 ` Eli Zaretskii
2008-04-15 20:35 ` David Kastrup
2008-04-16 20:15 ` Stephen J. Turnbull
2008-04-16 20:32 ` David Kastrup
2008-04-17 3:23 ` Stephen J. Turnbull
2008-04-17 3:26 ` Eli Zaretskii
2008-04-17 7:44 ` Stephen J. Turnbull
2008-04-17 8:19 ` Jan Djärv
2008-04-17 12:41 ` Eli Zaretskii
2008-04-17 17:20 ` Stephen J. Turnbull
2008-04-17 18:03 ` Eli Zaretskii
2008-04-16 22:09 ` Eli Zaretskii
2008-04-17 1:14 ` Stefan Monnier
2008-04-14 20:20 ` Stefan Monnier
2008-04-14 20:58 ` David Kastrup
2008-04-14 22:19 ` Stefan Monnier
2008-04-14 22:26 ` David Kastrup
2008-04-14 22:33 ` Stefan Monnier
2008-04-15 5:44 ` David Kastrup
2008-04-15 15:35 ` Stefan Monnier
2008-04-14 21:35 ` Stephen J. Turnbull
2008-04-14 5:17 ` Kenichi Handa
2008-04-14 13:57 ` Stefan Monnier
2008-04-14 7:02 ` tomas
2008-04-14 17:45 ` Eli Zaretskii
2008-04-15 7:38 ` tomas
2008-04-15 22:30 ` Juri Linkov
2008-04-16 3:20 ` Eli Zaretskii
2008-04-16 8:12 ` Jason Rumney
2008-04-16 13:35 ` Stefan Monnier
2008-04-16 14:45 ` Jason Rumney
2008-04-16 17:05 ` Stefan Monnier
2008-04-16 20:09 ` Stephen J. Turnbull
2008-04-16 23:17 ` Juri Linkov
2008-04-16 23:42 ` Jason Rumney
2008-04-17 1:03 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uskxoqnph.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.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.