> On Mon, 3 Apr 2017 14:12:51 +0700
> "Gerriet M. Denkmann" wrote:
>
>> The Combining Class is used for normalisation of strings.
>> Normalisation of strings is important for filenames in filesystems.
>>
>> As far as I know, a Thai consonant (Lo, Other_Letter) can have
>> several Nonspacing_Mar
Den 2017-04-04 00:35, skrev "Michael Everson" :
>> What I am saying is that the glyphs for the two new variants you are
>> proposing need to harmonise with the block elements such as U+2581
>> LOWER ONE EIGHTH BLOCK.
>
> No in a chess font the font designer has to draw those block-element
> cha
Den 2017-04-04 03:12, skrev "Michael Everson" :
> It *is* important that there be an even number of characters in every row of 8
> squares for fallback display to be better rather than worse, I think.
I agree. (Though *at present*, I happen to get a visible display of the
VSs in the email app, w
Den 2017-04-04 03:21, skrev "Asmus Freytag" :
> would look like this, if you base your proposal on ligatures rather than
> variation selectors (minimal case A above):
>
> ▕□︀▨︁□︀▨︁♙︁□︀♛︀▨︁□︀▨︁▏
That line has a lot of VSs in it... (I see them, since they happen to be
visible in the email app I
On 4/3/2017 4:30 PM, Michael Everson
wrote:
The next question would be whether the alternation in background is best expressed in variation sequences or by some other means.
I think the value in the data structures I have described is best ret
> On 4 Apr 2017, at 02:01, Kent Karlsson wrote:
>
>>> Book formatting? Old style book formatting still cannot use as
>>> sophisticated layouts as HTML can... (AFAIK).
>>
>> Yeah, but come on, the chief use of chess characters is to cite them inline
>> in text like any other symbol @ § % & and
Den 2017-04-04 02:10, skrev "Michael Everson" :
> On 4 Apr 2017, at 00:45, Kent Karlsson wrote:
>>
>> Book formatting? Old style book formatting still cannot use as sophisticated
>> layouts as HTML can... (AFAIK).
>
> Yeah, but come on, the chief use of chess characters is to cite them inline
> I'm trying to work out whether we need a variation sequence for
> "chesspiece in a sentence”.
Of course! Haven’t you ever seen chess problem texts? Check out the Fairy Chess
proposal for encoding additional characters. Plenty of examples there.
Sorry, I meant “Of course **not**!” that is, che
On 4 Apr 2017, at 00:59, Richard Wordingham
wrote:
> No, he wants two characters WHITE CHESS KNIGHT and WHITE CHESS KNIGHT ON DARK
> BACKGROUND, and a variation selector, say VS2, that when applied to them
> yields a glyph that works with block elements.
>
> It might be simpler if WHITE CHESS
On 4 Apr 2017, at 00:47, Richard Wordingham
wrote:
> I'm trying to work out whether we need a variation sequence for
> "chesspiece in a sentence”.
Of course! Haven’t you ever seen chess problem texts? Check out the Fairy Chess
proposal for encoding additional characters. Plenty of examples the
On 4 Apr 2017, at 00:45, Kent Karlsson wrote:
>
> Book formatting? Old style book formatting still cannot use as sophisticated
> layouts as HTML can... (AFAIK).
Yeah, but come on, the chief use of chess characters is to cite them inline in
text like any other symbol @ § % & and the other equal
On 3 Apr 2017, at 23:53, Asmus Freytag wrote:
> Alternatively, a system that uses no Variation selectors and only relies on
> Opentype ligatures might work even better.
>
> This would require one Empty and one Filled board cell, to ligate with
> whatever piece is supposed to sit on top of it.
On Tue, 4 Apr 2017 00:30:30 +0100
Michael Everson wrote:
> On 3 Apr 2017, at 23:07, Asmus Freytag (c)
> wrote:
> You want WHITE CHESS KNIGHT, and WHITE CHESS KNIGHT ON SQUARE, and
> use a VS that changes the colour of the square? That is less legible
> in plain text than my proposal. Not as goo
On Mon, 3 Apr 2017 23:35:52 +0100
Michael Everson wrote:
> On 3 Apr 2017, at 22:03, Richard Wordingham
> wrote:
The relevant text before was,
"I'm talking about looking for a U+2654 glyph for ordinary text when
all the first font tried has is:
2654 FE01; Chesspiece on white; # WHITE CHESS KI
I can well imagine people deeply interested in chess, to want to exchange
chess board layouts
in plain text emails (or at least not use quite hard-to-handle HTML code),
and even parse them
(programmatically) for analysis by a program, not wanting to bother with
quite complex HTML/CSS stuff.
Includ
On 3 Apr 2017, at 23:34, Richard Wordingham
wrote:
>
>> Leave the question of requesting M-square metrics to a (single) variation
>> selector and you are done.
>
> This solution quiets my qualms.
It does not meet my requirement, and it solves no problem.
Michael Everson
On 3 Apr 2017, at 23:07, Asmus Freytag (c) wrote:
>
> On 4/3/2017 2:15 PM, Michael Everson wrote:
>> On 3 Apr 2017, at 17:16, Asmus Freytag wrote:
>>
> The same indirection is at play here.
>
This is pure rhetoric, Asmus. It addresses the problem in no way.
>>> Actually it d
On 4/3/2017 3:28 PM, Richard Wordingham
wrote:
On Mon, 3 Apr 2017 22:48:31 +0100
Michael Everson wrote:
Yes, this is what I’ve proposed.
I was explaining it to Asmus and others with similar misunderstandings.
Richard.
A
Markus, that there exist dozens of fonts designed for chessboard typesetting
should suggest that people wish to use computers to do so. There are many, many
volumes published on chess problems and there are some people who are
passionately interested in that very specific intellectual pursuit.
On 3 Apr 2017, at 22:03, Richard Wordingham
wrote:
> Nobody said the glyphs for use in ordinary text had to be a fixed width.
That’s why there’s a non-variant state and then two “on-square” variant states.
If you want to construct a chessboard using a font, whether it is using an
ASCII font
On Mon, 3 Apr 2017 15:07:38 -0700
"Asmus Freytag (c)" wrote:
> Having the system use specific character codes for the empties and
> variation selectors for the pieces is a needless complication; just
> duplicate the few pieces with a hatched background. (The precise
> style of hatching should b
On Mon, 3 Apr 2017 22:48:31 +0100
Michael Everson wrote:
> Yes, this is what I’ve proposed.
I was explaining it to Asmus and others with similar misunderstandings.
Richard.
On 4/3/2017 2:15 PM, Michael Everson wrote:
On 3 Apr 2017, at 17:16, Asmus Freytag wrote:
The same indirection is at play here.
This is pure rhetoric, Asmus. It addresses the problem in no way.
Actually it does. I'm amazed that you don't see the connection.
I’ve never understood you when yo
On 3 Apr 2017, at 20:58, Asmus Freytag wrote:
>
> On 4/3/2017 12:33 PM, Richard Wordingham wrote:
>> If the variation selectors are ignored, these simplify to:
>>
>> white square
>> hatched square
>> specific piece
>>
>> This preserves all the information; the pattern of squares is known in
>>
On 3 Apr 2017, at 20:33, Richard Wordingham
wrote:
> There was no intention to encode the bishops separately. It just happens
> that the rules of chess allow one to distinguish the bishops
> simply by recording the colour of the square they are currently on.
That only works for them though.
On Mon, Apr 3, 2017 at 2:33 PM, Michael Everson
wrote:
> On 3 Apr 2017, at 18:51, Markus Scherer wrote:
>
>
> It seems to me that higher-level layout (e.g, HTML+CSS) is appropriate for
> the board layout (e.g., via a table), board frame style, and cell/field
> shading. In each field, the existin
Richard,
The emoji and text presentation sequences were moved to the UTS #51 data file
emoji-variation-sequences.txt, which is new in Version 5.0 of the UTS. Please
see
http://www.unicode.org/Public/emoji/5.0/emoji-variation-sequences.txt
The move is documented on the Beta Unicode 10.0 pa
On 3 Apr 2017, at 18:51, Markus Scherer wrote:
>
> It seems to me that higher-level layout (e.g, HTML+CSS) is appropriate for
> the board layout (e.g., via a table), board frame style, and cell/field
> shading. In each field, the existing characters should suffice.
That isn’t plain text.
Thi
Den 2017-04-03 20:46, skrev "Kent Karlsson" :
>
> Den 2017-04-03 19:51, skrev "markus@gmail.com" :
>
>> > It seems to me that higher-level layout (e.g, HTML+CSS) is appropriate for
>> the
>> > board layout (e.g., via a table), board frame style, and cell/field
>> shading.
>> > In each fiel
> On 3 Apr 2017, at 17:18, Asmus Freytag wrote:
>
> On 4/3/2017 5:12 AM, Michael Everson wrote:
>>> I'm not convinced that it is. A player starts with two non-interchangeable
>>> bishops. could only refer the white bishop that is
>>> restricted to black squares. That's a semantic difference
On 3 Apr 2017, at 17:16, Asmus Freytag wrote:
>>> The same indirection is at play here.
>> This is pure rhetoric, Asmus. It addresses the problem in no way.
> Actually it does. I'm amazed that you don't see the connection.
I’ve never understood you when you back up into that particular kind of
Where in the draft databases for Unicode 10.0 is Unicode 9.0 variation
sequence declared legitimate? Without such a
declaration, a font that had a special glyph for or
a substitution specific to would not be Unicode compliant.
I hope this reflects my ignorance of the definition system rather t
On Mon, 3 Apr 2017 14:12:52 +0200
Michael Everson wrote:
> On 2 Apr 2017, at 18:27, Richard Wordingham
> wrote:
> I think you are seriously going the wrong way with this thinking. The
> immediate parallel that comes to mind are things like:
>
> 1000 MYANMAR LETTER KA
> ⁓ 1000 FE00 dotted f
On Mon, Apr 3, 2017 at 9:33 PM, Richard Wordingham
wrote:
> On Sun, 2 Apr 2017 10:43:39 -0700
> Asmus Freytag wrote:
>
>> In these cases, explicit encoding would better cover what is desired:
>> a reliable way to mark a distinction between different symbols (the
>> two bishops are separate symbol
2017-04-03 20:13 GMT+02:00 William_J_G Overington :
>
> A tag sequence for this purpose starts with a capital letter V standing
> for vector format.
>
> At the start of the sequence a:=255; b:=0; g:=0; m:=1; p:=0; r:=0; x:=0;
> y:=0; w:=1000;
>
> At the start of the sequence the points buffer is e
On 4/3/2017 12:33 PM, Richard
Wordingham wrote:
If the variation selectors are ignored, these simplify to:
white square
hatched square
specific piece
This preserves all the information; the pattern of squares is known in
advance and therefore redundant.
T
On Sun, 2 Apr 2017 10:43:39 -0700
Asmus Freytag wrote:
> In these cases, explicit encoding would better cover what is desired:
> a reliable way to mark a distinction between different symbols (the
> two bishops are separate symbols, that also happen to express
> distinct, though related concepts
On Mon, 3 Apr 2017 14:12:51 +0700
"Gerriet M. Denkmann" wrote:
> The Combining Class is used for normalisation of strings.
> Normalisation of strings is important for filenames in filesystems.
>
> As far as I know, a Thai consonant (Lo, Other_Letter) can have
> several Nonspacing_Marks. This clu
Den 2017-04-03 19:51, skrev "markus@gmail.com" :
> It seems to me that higher-level layout (e.g, HTML+CSS) is appropriate for the
> board layout (e.g., via a table), board frame style, and cell/field shading.
> In each field, the existing characters should suffice.
>
> markus
True, and one
It seems to me that higher-level layout (e.g, HTML+CSS) is appropriate for
the board layout (e.g., via a table), board frame style, and cell/field
shading.
In each field, the existing characters should suffice.
markus
Peter Constable wrote:
> William, you completely miss the point: As long as Unicode is the way to
> provide emoji to consumers, their needs and desires will not be best or fully
> met. Unicode as an AND gate is too many AND gates.
Ah, I understand what you mean now.
In my feedback of 7 March
On 4/3/2017 12:12 AM, Gerriet M. Denkmann wrote:
The Combining Class is used for normalisation of strings.
Normalisation of strings is important for filenames in filesystems.
The same issues apply to network identifiers.
As far as I know, a Thai consonant (Lo, Other_Letter) can have several
On 4/3/2017 5:12 AM, Michael Everson
wrote:
I'm not convinced that it is. A player starts with two non-interchangeable bishops. could only refer the white bishop that is restricted to black squares. That's a semantic difference.
Surely not.
On 4/3/2017 5:42 AM, Michael Everson wrote:
Read to the end.
On 2 Apr 2017, at 19:43, Asmus Freytag wrote:
It's a matter of perspective.
Higher-level semantic constructs are encoded in writing (or graphic notation),
and you can see the individual marks, signs, letters and symbols as the ele
The Combining Class is used for normalisation of strings.
Normalisation of strings is important for filenames in filesystems.
As far as I know, a Thai consonant (Lo, Other_Letter) can have several
Nonspacing_Marks.
This cluster of nonspacing marks can contain at most one top/bottom vowel and
at
Den 2017-04-03 14:50, skrev "Michael Everson" :
> On 2 Apr 2017, at 18:52, Richard Wordingham
> wrote:
>>
>> You forgot the most important setting though - that the higher-order
>> protocols allow symbols to be displayed left-to-right. If the direction
>> should happen to be right-to-left, no
On 2 Apr 2017, at 18:52, Richard Wordingham
wrote:
>
> You forgot the most important setting though - that the higher-order
> protocols allow symbols to be displayed left-to-right. If the direction
> should happen to be right-to-left, not only is the game mirrored, but the
> board edges don't
On 2 Apr 2017, at 19:43, Asmus Freytag wrote:
> It's a matter of perspective.
>
> Higher-level semantic constructs are encoded in writing (or graphic
> notation), and you can see the individual marks, signs, letters and symbols
> as the element of this encoding. However, how strongly any of th
On 2 Apr 2017, at 18:27, Richard Wordingham
wrote:
> We seem to agree that it should be a graphic modification, rather than as
> semantic modification.
Yes, we do.
> The question I pose is, "Is it just a graphic modification in this case?".
Yes, it is.
> I'm not convinced that it is. A
2017-04-03 12:31 GMT+02:00 Martin J. Dürst :
> Also it would be weird to try e.g. to "semantically" distinguish the two
> rooks, even if they are two different actual chess pieces on an actual
> board.
>
However it is perfectly possible to have pseudo-variants using pieces and
an annotation on th
On 2017/04/03 01:27, Richard Wordingham wrote:
We seem to agree that it should be a graphic modification, rather than
as semantic modification. The question I pose is, "Is it just a
graphic modification in this case?". I'm not convinced that it is. A
player starts with two non-interchangeable
51 matches
Mail list logo
