On Fri, 4 Jan 2013 14:19:15 -0800
Markus Scherer markus@gmail.com wrote:
It is sometimes useful to design very low-level data structures or
algorithms in alignment with some block boundaries, but they are
really just artifacts of previous character allocations, and for
nearly all text
On 1/4/2013 2:36 AM, Stephan Stiller wrote:
All,
There are plenty of unassigned code points within blocks that are in
use; these often come at the end of a block but there are plenty of
holes as well.
I have a cluster of interrelated questions:
1. What sorts of reasons are there (or have
There's no distinction between holes and other unassigned characters.
Good to know. This might be important knowledge for people using block
ranges loosely for algorithms that deal with Unicode text.
2.2 If yes, how does the number of assigned code points differ, if
holes that are assumed
It's generally not desirable, but there's no firm policy that blocks
must have a single script value (and in fact, no such restriction
exists in existing blocks).
If strong technical reasons exist for placing a character into the
BMP, there will be temptation to fill a hole if the BMP is
2013/1/4 Asmus Freytag asm...@ix.netcom.com:
On 1/4/2013 2:36 AM, Stephan Stiller wrote:
All,
There are plenty of unassigned code points within blocks that are in use;
these often come at the end of a block but there are plenty of holes as
well.
I have a cluster of interrelated questions:
Stephan Stiller continued:
Occasionally the question is asked how many characters Unicode has. This
question has an answer in section D.1 of the Unicode Standard. I
suspect, however, that once in a while the motivation for asking this
question is to find out how much of Unicode has been used
Whoops!
http://www.unicode.org/alloc/CurrentAllocation.html
--Ken
The editors maintain some statistical information relevant to this fun
question
at:
http://www.unicode.org/alloc/CurrentAllocaiton.html
On 4 Jan 2013, at 18:24, Whistler, Ken ken.whist...@sap.com wrote:
There have been a few notable examples where particularly egregious examples
of holes in blocks that seemed unlikely to be filled with like material in
the future were reprogrammed as it were, and grabbed for the encoding of
http://www.unicode.org/alloc/CurrentAllocaiton.html
=
http://www.unicode.org/alloc/CurrentAllocation.html
Mark https://plus.google.com/114199149796022210033
*
*
*— Il meglio è l’inimico del bene —*
**
On Fri, Jan 4, 2013 at 10:24 AM, Whistler, Ken ken.whist...@sap.com wrote:
Stephan Stiller
On Fri, Jan 4, 2013 at 5:32 AM, Stephan Stiller
stephan.stil...@gmail.comwrote:
There's no distinction between holes and other unassigned characters.
Good to know. This might be important knowledge for people using block
ranges loosely for algorithms that deal with Unicode text.
It is
10 matches
Mail list logo
