From: tomas@tuxteam.de
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: utf-16le vs utf-16-le
Date: Tue, 15 Apr 2008 07:38:24 +0000 [thread overview]
Message-ID: <20080415073824.GA8466@www.trapp.net> (raw)
In-Reply-To: <uve2kqqir.fsf@gnu.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, Apr 14, 2008 at 08:45:32PM +0300, Eli Zaretskii wrote:
> > Date: Mon, 14 Apr 2008 07:02:14 +0000
> > Cc: emacs-devel@gnu.org
> > From: tomas@tuxteam.de
> >
> > > I tripped over these when I tried to read debugging logs saved by
> > > MS-Windows, which are in UTF-16 without a BOM: [...]
> >
> > This is courtesy of the same folks who like to put BOMs in UTF-8. I'm
> > speechless (again).
>
> Actually, I don't necessarily see anything wrong with the lack of BOM
> in this case: these are Windows-internal log files, meant to be read
> by utilities who know the encoding, not by general-purpose text
> editors. UTF-16 is the native encoding used by Windows low-level APIs
> and the kernel for non-ASCII text, so seeing that in a temporary file
> shouldn't be a surprise. And of course, Windows doesn't need a BOM
> because it uses only one endianness.
Absolutely. I do agree on all this -- it was the stark contrast of not
using BOM sometimes in utf-16 to using BOM in UTF-8 what caused ummm...
some emotions ;-)
> A BOM in UTF-8 is another matter, of course...
Both things taken together make the work of art.
Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFIBFtwBcgs9XrR2kYRAtpuAJ9beaO8hnA+9E9ZwYOGHivuUzsaDgCeKc2t
Jia4zA34M29IAI0AJrd7NyA=
=msxe
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-04-15 7:38 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
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 [this message]
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=20080415073824.GA8466@www.trapp.net \
--to=tomas@tuxteam.de \
--cc=eliz@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 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.