From: Johannes Sixt <j6t@kdbg.org>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, "Lars Schneider" <larsxschneider@gmail.com>,
"Torsten Bögershausen" <tboegi@web.de>
Subject: Re: [PATCH 0/2] Improve documentation on UTF-16
Date: Fri, 28 Dec 2018 09:59:05 +0100 [thread overview]
Message-ID: <34d4f912-2ec3-9dd1-f5fb-aad6a26e1464@kdbg.org> (raw)
In-Reply-To: <20181227234535.GD423984@genre.crustytoothpaste.net>
Am 28.12.18 um 00:45 schrieb brian m. carlson:
> On Thu, Dec 27, 2018 at 08:55:27PM +0100, Johannes Sixt wrote:
>> But why do you add another U+FEFF on the way to UTF-8? There is one in the
>> incoming UTF-16 data, and only *that* one must be converted. If there is no
>> U+FEFF in the UTF-16 data, the should not be one in UTF-8, either.
>> Puzzled...
>
> So for UTF-16, there must be a BOM. For UTF-16LE and UTF-16BE, there
> must not be a BOM. So if we do this:
>
> $ printf '\xfe\xff\x00\x0a' | iconv -f UTF-16BE -t UTF-16 | xxd -g1
> 00000000: ff fe ff fe 0a 00 ......
What sort of braindamage is this? Fix iconv.
But as I said, I'm not an expert. I just vented my worries that
widespread existing practice would be ignored under the excuse "you are
the outlier".
-- Hannes
next prev parent reply other threads:[~2018-12-28 8:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 2:17 [PATCH 0/2] Improve documentation on UTF-16 brian m. carlson
2018-12-27 2:17 ` [PATCH 1/2] Documentation: document UTF-16-related behavior brian m. carlson
2018-12-27 2:17 ` [PATCH 2/2] utf8: add comment explaining why BOMs are rejected brian m. carlson
2018-12-27 10:06 ` [PATCH 0/2] Improve documentation on UTF-16 Johannes Sixt
2018-12-27 16:43 ` brian m. carlson
2018-12-27 19:55 ` Johannes Sixt
2018-12-27 23:45 ` brian m. carlson
2018-12-28 8:59 ` Johannes Sixt [this message]
2018-12-28 20:31 ` Philip Oakley
2018-12-28 8:46 ` Ævar Arnfjörð Bjarmason
2018-12-28 20:35 ` Philip Oakley
2018-12-29 23:17 ` brian m. carlson
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34d4f912-2ec3-9dd1-f5fb-aad6a26e1464@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=sandals@crustytoothpaste.net \
--cc=tboegi@web.de \
/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://80x24.org/mirrors/git.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).