From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: UTF-8 character encoding
Date: Wed, 27 Jun 2018 09:31:00 -0000 [thread overview]
Message-ID: <CAD8GWstSXHT0xFXbrzQNcOCdME7p2zRLSRffJe4BjhFuP48-Bw@mail.gmail.com> (raw)
In-Reply-To: <981ba1fe-7961-5ed0-e3c7-a5717af8c141@towo.net>
On 6/26/18, Thomas Wolff wrote:
> This encoding scheme is wrong; where did you get it from? Maybe it's the
> obsolete UTF-8...
http://www.cl.cam.ac.uk/~mgk25/ucs/utf-8-history.txt
I thought I saw something about utf-8 being able to handle a 31 bit
value.. is that also obsolete/wrong?
how about this for the current encoding scheme:
http://www.unicode.org/versions/Unicode11.0.0/ch03.pdf
Table 3-6. UTF-8 Bit Distribution
Bits Scalar Value First Byte Second Byte Third Byte
Fourth Byte
7 00000000 0xxxxxxx 0xxxxxxx
11 00000yyy yyxxxxxx 110yyyyy 10xxxxxx
16 zzzzyyyy yyxxxxxx 1110zzzz 10yyyyyy 10xxxxxx
21 000uuuuu zzzzyyyy yyxxxxxx 11110uuu 10uuzzzz 10yyyyyy 10xxxxxx
Lee
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-06-27 6:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 7:20 Lee
2018-06-21 10:12 ` Stefan Weil
2018-06-21 10:39 ` Andrey Repin
2018-06-22 7:31 ` Lee
2018-06-22 17:30 ` Andrey Repin
2018-06-25 9:56 ` L A Walsh
2018-06-25 20:52 ` Lee
2018-06-26 21:39 ` Thomas Wolff
2018-06-27 9:31 ` Lee [this message]
2018-06-27 7:50 ` Michael Enright
2018-06-27 9:34 ` Lee
2018-06-21 18:49 ` Houder
2018-06-21 20:46 ` Houder
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=CAD8GWstSXHT0xFXbrzQNcOCdME7p2zRLSRffJe4BjhFuP48-Bw@mail.gmail.com \
--to=ler762@gmail.com \
--cc=cygwin@cygwin.com \
/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.
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).