Of course it’s not “misleading”. Human language is best conveyed by text.
Michael Everson
> On 19 Nov 2019, at 18:59, Costello, Roger L. via Unicode
> wrote:
>
> Hi Folks,
>
> Today I received an email from the Unicode organization. The email said this:
> (italics an
No, thank you.
> On 31 May 2019, at 11:18, bristol_poo via Unicode wrote:
>
> Greetings,
>
> I hope I dont intrude too much on this list with a proposal.
>
> U+1F4A9, aka the 'pile of poo' emoji, has gained somewhat of a legendary
> status in the modern society [1].
>
> With the somewhat re
doubt such exists :-)
You are the type designer. You may live in the 21st century, but you could just
as easily have lived in the 16th. Your client says “I need a Ꝭ glyph” and it’s
up to you to design one. The easiest thing for your purposes (since you may not
find a capital Ꝭ easily is to t
Fredrick,
> I sent this query to Michael Everson directly on Feb. 19 but did not hear
> anything back. I assume that he was too busy to respond, perhaps I even broke
> some unwritten rule of etiquette, for which I apologize; so I am hoping that
> someone on the mailing list know
My question was why it was needed to have both
> spirals as different characters instead of a single one that can be either,
> as the proposal didn't specify an use case where there is a semantic
> difference between each one.
>
>
> El sáb., 16 feb. 2019 a las
t.
Clockwise and anticlockwise are not the same thing.
Michael Everson
The hell I do, Julian.
http://evertype.com/polynesian.html
> On 27 Jan 2019, at 21:00, Julian Bradfield via Unicode
> wrote:
>
> You have a very low opinion of Polynesian users.
Yes, yes. It doesn’t matter. The discussion applies to both the two quotation
marks and the two modifier letters.
> On 27 Jan 2019, at 15:08, Tom Gewecke via Unicode wrote:
>
>
>> On Jan 26, 2019, at 11:08 PM, Richard Wordingham via Unicode
>> wrote:
>>
>> It may be a matter of literacy in
but isn't the correct
> encoding for the ʻokina U+02BB MODIFIER LETTER TURNED COMMA?
Yes, but both 02BB and 02BC are used in linguistic transcriptions and in
Polynesian languages, and the graphic identity with 2018 and 2019 is
problematic and unnecessary.
Using 02BC for the apostrophe is a mistake, in my view.
Michael Everson
Fair enough, but I didn’t wait.
> On 27 Jan 2019, at 01:59, James Kass via Unicode wrote:
>
>
> Richard Wordingham responded to Michael Everson,
>
> >> I’ll be publishing a translation of Alice into Ancient Greek in due
> >> course. I will absolutely only
or 02BC were to be changed, it would in no case
impact adversely on scientific linguistics texts. It would just make the mark a
bit bigger. But for practical use in Polynesian languages where the character
has to be found alongside the quotation marks, a glyph distinction must be made
between this and punctuation.
Michael Everson
Polynesians are using 0027 as a fallback, and this has to do with education,
keyboarding, and training.
The typography of the fallback is of no consequence. It’s a fallback.
> On 27 Jan 2019, at 01:43, Richard Wordingham via Unicode
> wrote:
>
> On Sat, 26 Jan 2019 17:11:49 -0800
> Asmus Frey
I’ll be publishing a translation of Alice into Ancient Greek in due course. I
will absolutely only use U+2019 for the apostrophe. It would be wrong for lots
of reasons to use U+02BC for this.
Moreover, implementations of U+02BC need to be revised. In the context of
Polynesian languages, it is i
should
have been made into an emoji at the same time when flags for Scotland, Wales,
and England were made. And it still should.
Michael Everson
character
or that I should use Ƶ rather than Z when I write *Ƶanƶibar.
Michael Everson
> On 2 Nov 2018, at 09:48, James Kass via Unicode wrote:
>
> A third possibility is that the double-underlined superscript was a
> writing/spelling convention of the time for writing/spelling abbreviations.
ither _meaningful_ or necessary.
Michael Everson
> On 28 Oct 2018, at 21:43, Piotr Karocki wrote:
>
>> The squiggle in your sample, Janusz, does not indicate anything; it is only
>> a decoration, and the abbreviation is the same without it.
>
> I disagreee. This squiggle means &
not indicate anything; it is only a decoration, and the
abbreviation is the same without it.
Michael Everson
> On 28 Oct 2018, at 17:28, Janusz S. Bień via Unicode
> wrote:
>
> For me only the latter seems acceptable. Using COMBINING LATIN SMALL
> LETTER R is a natural idea, bu
rules differ. “The Fellowship of the
Ring” is acceptable in English. “The Fellowship Of The Ring” is not.
Michael Everson
> On 28 Jul 2018, at 18:01, Kent Karlsson wrote:
>
> I know it is too late now, but... Could have added the characters,
> without adding the case mappings. Just as
Mtavruli could not be represented in the UCS before we added these characters.
Now it can.
Michael Everson
> On 28 Jul 2018, at 14:10, Richard Wordingham via Unicode
> wrote:
>
> On Sat, 28 Jul 2018 01:45:53 +
> Peter Constable via Unicode wrote:
>
>> (ii
On 27 Jul 2018, at 13:42, James Kass via Unicode wrote:
>
> MIchael Everson wrote,
>
>> No, James is mistaken. Georgian is structurally casing, and the difference
>> is not stylistic, but orthographic.
>
> I am not mistaken; I never said Georgian wasn't structu
ally, but I have to check those
> books first.)
What is “formal validity”? Those books exist. They are facts. We analyse
material in order to describe the structure of scripts.
Michael Everson
On 27 Jul 2018, at 13:37, Alexey Ostrovsky via Unicode
wrote:
>
> On Fri, Jul 27, 2018 at 3:58 PM, Michael Everson via Unicode
> wrote:
>
> Then how can you prove it is a case and not a stylistic variation? Let's
> compare with a case of Hebrew or Arabic, for e
On 27 Jul 2018, at 13:28, Alexey Ostrovsky via Unicode
wrote:
>
> On Fri, Jul 27, 2018 at 3:44 PM, Michael Everson via Unicode
> wrote:
>> You have me to thank for undoing that mistake. And some other mistakes. We
>> all make mistakes.
>
> I would like to av
text, which is what they want to do.
Michael Everson
> On 27 Jul 2018, at 13:11, Alexey Ostrovsky via Unicode
> wrote:
>
> On Fri, Jul 27, 2018 at 3:34 PM, James Kass via Unicode
> wrote:
> There's nothing preventing the Georgian user community to continue to
>
On 27 Jul 2018, at 12:22, Alexey Ostrovsky via Unicode
wrote:
>
> It is a mistake or misinterpretation of evidence provided (modern samples and
> samples from 19th c., provided in N4712 in the same context, are of different
> nature, it is clear even from images) and §8 of the document states
letters are encoded. Previously it would not have been possible to do so,
since small caps is a fancy-text style of presenting lowercase letters with
uppercase glyphs.
Mtavruli is not small caps. Mtavruli is ALL CAPS.
Michael Everson
titlecase. It’s just
that that orthography is no longer in use and that behaviour no longer
desirable.
Michael Everson
> On 27 Jul 2018, at 05:54, James Kass via Unicode wrote:
>
> Alexey Ostrovsky wrote,
>
>> "The Georgian community understood" — sorry, but
>
“moving its content” to CLDR makes no sense.
Michael Everson
> On 12 Jun 2018, at 16:20, Marcel Schneider via Unicode
> wrote:
> On Tue, 12 Jun 2018 15:58:09 +0100, Michael Everson via Unicode wrote:
>>
>> Marcel,
>> You have put words into my mouth. Please don’t.
Marcel,
You have put words into my mouth. Please don’t. Your description of what I said
is NOT accurate.
> On 12 Jun 2018, at 03:53, Marcel Schneider via Unicode
> wrote:
>
> And in this thread I wanted to demonstrate that by focusing on the wrong
> priorities, i.e. legacy character names i
n CLDR.
Synchronization with an unused ISO standard is not necessary to do that.
Michael Everson
On 7 Jun 2018, at 20:13, Marcel Schneider via Unicode
wrote:
> On Fri, 18 May 2018 00:29:36 +0100, Michael Everson via Unicode responded:
>>
>> It would be great if mutual synchronization were considered to be of benefit.
>> Some of us in SC2 are not happy that the U
t; for modern system requirement, no particular industry support, and scant
> content: see Wikipedia for "The registry has not been updated since December
> 2001”.)
Mark is right.
Michael Everson
I consider it a significant semantic shift from the intended meaning of the
character in the source Japanese character set.
Michael Everson
It would be great if mutual synchronization were considered to be of benefit.
Some of us in SC2 are not happy that the Unicode Consortium has published
characters which are still under Technical ballot. And this did not happen only
once.
> On 17 May 2018, at 23:26, Peter Constable via Unicode
It sounds to me like a fault in the keyboard software, which could be fixed by
the people who own and maintain that software.
> On 17 May 2018, at 01:20, Richard Wordingham via Unicode
> wrote:
>
> On Thu, 17 May 2018 00:34:35 +0100
> Michael Everson via Unicode wrote:
>
And Icelandic. And Irish. And so on.
> On 16 May 2018, at 23:41, Anshuman Pandey via Unicode
> wrote:
>
>> 2. Collation is different between the Assamese and Bengali languages,
>> and code point order should reflect collation order.
>
> The same issue applies to dictionary order for Hindi, Ma
This is not a fault of the encoding.
> On 16 May 2018, at 23:01, Richard Wordingham via Unicode
> wrote:
>
> I think simple Windows keyboards have a limit of 4 16-bit code units;
> for an Indic SMP script, one couldn't map to a single key, as it
> would require 6 code units.
I absolutely disagree. There’s a whole lot of related languages out there, and
the speakers share some things in common. Orthographic harmonization between
these languages can ONLY help any speaker of one to access information in any
of the others. That expands people’s worlds. That would be a g
Stalin would be very pleased. Divide and conquer.
> On 21 Feb 2018, at 01:15, Garth Wallace via Unicode
> wrote:
>
> AIUI "doesn't look like Turkish" was one of the design criteria, for
> political reasons.
>
> On Tue, Feb 20, 2018 at 1:07 PM Michael
, and I bet you anything
there will be ambiguity where some morpheme ends in -s and the next begins with
h- where you have [sx] and not [ʃ].
Groan.
> On 20 Feb 2018, at 20:40, Christoph Päper wrote:
>
> Michael Everson:
>> Why on earth would they use Ch and Sh when 1) C isn’t
Why on earth would they use Ch and Sh when 1) C isn’t used by itself and 2) if
you’re using Ǵǵ you may as well use Çç Şş.
Groan.
> On 20 Feb 2018, at 19:40, Christoph Päper via Unicode
> wrote:
>
> Apparently the presidential decree prescribing the new Kazakh Latin
> orthography and alphabet
I won’t.
> On 19 Jan 2018, at 13:51, Andrew West via Unicode wrote:
>
> On 19 January 2018 at 13:19, Michael Everson via Unicode
> wrote:
>>
>> I’d go talk with him :-) I published Alice in Kazakh. He might like that.
>
> Damn, you'll have to reprint it with apostrophes now.
>
> Andrew
>
There’s no redeeming this orthography.
> On 19 Jan 2018, at 13:42, Philippe Verdy via Unicode
> wrote:
>
> Hmmm that character exists already at 0+0315 (a combining comma above
> right). It would work for the new Kazah orthographic system, including for
> collation purpose. I don't thin
I’d go talk with him :-) I published Alice in Kazakh. He might like that.
Michael
> On 19 Jan 2018, at 09:39, Andrew West via Unicode wrote:
>
> On 19 January 2018 at 09:16, Shriramana Sharma via Unicode
> wrote:
>> Wow. Somebody really needs to convey this to the Kazhaks. Else a
>> short-sig
g like it or derived from it
ended up devising capital letters.
Doke’s click letters are better candidates for encoding.
Michael Everson
PH O006B
> 𓉚U+1325A EGYPTIAN HIEROGLYPH O006C
> 𓊆U+13286 EGYPTIAN HIEROGLYPH O036A
> 𓊈U+13288 EGYPTIAN HIEROGLYPH O036C
> Egyptian Hieroglyphs — V. Rope, fiber, baskets, bags, etc.items: 1
>
> 𓍹 U+13379 EGYPTIAN HIEROGLYPH V011A
These properties were chosen explicitly when Egyptian was first defined. Those
are enclosing punctuation characters.
Michael Everson.
transcriptions.
Why should visibility matter here?
Michael Everson
> So I decided to make a post.
>
> Kazunari Tsuboi
>
> -Original Message-
> From: Michael Everson [mailto:ever...@evertype.com]
> Sent: Wednesday, October 4, 2017 11:31 PM
> To: Tsuboi, Kazunari
> Cc: unicode Unicode Discussion
> Subject: Re: Question about Karaba
They are not encoded, but that example is not sufficient. If you’d like to
contact me offline we can discuss this further.
Michael Everson
> On 4 Oct 2017, at 08:39, via Unicode wrote:
>
> Hi there,
>
> The Karabakh language uses Armenian characters, but the following chara
“The uniqueness of the Assamese script was perhaps unknown to the mainly
American experts of Unicode, sources said.”
They have never been able to show the difference to anyone in SC2 (which has
more than Americans in it), because there is no difference to show.
Michael Everson
> On 23
Now that it has been added, however, the situation is different.
> On 2 Jul 2017, at 16:59, Jörg Knappen via Unicode wrote:
>
> > Is it possible to design fonts that will render ẞ as SS?
>
> In fact, that has happened long before the capital letter sharp s was added
> to Unicode: The T1 enco
ce
> hyphenation is not
> influenced by the ß→SS substitution). However, in Switzerland it gets
> hyphenated as `STRAS-SE', since Swiss German doesn't use ß; instead,
> `ss' gets treated as a normal double consonant.
It would be hyphenated STRA-ẞE in any case.
Michael Everson
It would be sensible to case-map ß to ẞ however.
> On 30 Jun 2017, at 16:29, Otto Stolz via Unicode wrote:
>
> Hello,
>
> der Rat für deutsche Rechtschreibung which is responsible for the further
> development of the official German orthography has finally recognized LATIN
> CAPITAL LETTER SH
High 101F6, high 101F6, High FE4F… ♫
> On 21 Jun 2017, at 18:01, Ken Whistler via Unicode
> wrote:
>
> I wonder IF 9 times suffice,
> But IF more are required,
> I'll tweet ILY, tweet it twice --
> Since spelling's been retired.
>
>
> On 6/21/2017 8:37 AM, William_J_G Overington via Unicode
IECE;So;0;ON;N;
>
> Which seems insufficient…
Yes, we know. One thing at a time, please.
Michael Everson
haracters,
> simplified characters, cursive characters, or pictures) which I consider a
> font design issue, and explicitly did not seek to encode circled ideographs.
> My proposal was rejected, and a different proposal by Michael Everson
> (http://www.unicode.org/L2/L2016/16270-n4766-xiang
de.org] On Behalf Of William_J_G
> Overington
> Sent: Thursday, April 6, 2017 11:40 AM
> To: ever...@evertype.com; richard.wording...@ntlworld.com; unicode@unicode.org
> Subject: Re: Coloured Punctuation and Annotation
>
> Michael Everson wrote:
>
>> No. Here is an example of a fon
On 10 Apr 2017, at 17:30, Peter Constable wrote:
Sorry, Peter. I didn’t realize you weren’t talking about chess fonts.
Michael
On 10 Apr 2017, at 19:32, Peter Constable via Unicode
wrote:
>
> Michael, your two-tone effect can easily be added into your first font using
> COLR and CPAL tables, so that the one font can support a monochrome rendering
> that uses glyphs in which the swirls are fused with the letters, and c
always square. I didn't say anything about fonts used for chess
> diagrams here.
Square also does not mean “em-square sized” which is pretty much what you need
for chess diagrams.
That’s all.
Michael Everson
are, which helps to
facilitate fallback reading when the ligation is not available.
OK, nothing new has been offered on this topic for a long time. Thank you for
your support of the VS proposal, Christoph. Your supplementary proposals didn’t
make it better to achieve the goal: to remove the barrier to people using
Unicode instead of various mutually-incompatible dingbat fonts for something
they already regularly do.
Michael Everson
.
Thank you for your consideration, but I will stick with using the ⅛-block and
quadrant characters.
Michael Everson
> On 9 Apr 2017, at 18:02, Kent Karlsson wrote:
>
>
> Den 2017-04-06 01:25, skrev "Michael Everson" :
>
> > Oh, here. This is what I would add.
On 8 Apr 2017, at 22:23, Asmus Freytag wrote:
> Time for Sarasvati to pull the plug on this thread?
Useful input has been gratefully received. I thank those gave it.
Michael Everson
> On 8 Apr 2017, at 15:14, Philippe Verdy wrote:
>
> 2017-04-08 15:59 GMT+02:00 Michael Everson :
> >> We’re not proposing to “implement a game”.
> >
> > You were yourself speaking about applications, me too, not just a "game".
>
> No, I wasn’t.
&
Type fonts.
This has nothing to do with the proposal.
>> We’re not proposing to “implement a game”.
>
> You were yourself speaking about applications, me too, not just a "game".
No, I wasn’t.
Michael Everson
evolution or interaction
> with other features)...
This has nothing to do with our proposal, or with the current practice of the
chess commmunity.
Michael Everson
do NOT have a coherent model amongst any of
their hacks.)
Michael Everson
her VS characters are used for emoji.
Michael Everson
quot;The more you overtick the plumbing, the easier it is to stop up the drain.” —
Cmdr Montgomery Scott.
> * and then use ZWJ to combine them with letters/symbols to be centered within
> them (possibly some extended clusters such as letters+combining subscript
> digits in Scrabble)
Scrabble. My word.
No. The present proposal meets a particular need: To enable the UCS to be able
to set chess diagrams.
Michael Everson
, I could write and post the code in Adobe OT feature file
> notation required for `calt` to demonstrate that this would yield results as
> expected for all full-size 8*8 diagrams and even for many detail diagrams of
> a section of the board.
And when “calt” substitutions can’t be displayed? What kind of fallback do you
have?
Michael Everson
he outline, but that’s a specific glyph
for a specific purpose.
Michael Everson
another, different one is found, with a different derivation, then the second
is automatically pre-judged to be unified with the first and must be disunified
from it. That does not make sense, because we encode writing systems, not
sounds. My view on this has been consistent since I first embarked on this
work.
Michael Everson
On 6 Apr 2017, at 17:36, Rebecca Bettencourt wrote:
>
> At some point this should be taken off the main list since discussion will
> get very detailed very quickly.
>
> I agree. How should we get all the interested parties together?
Everybody interested, raise your hand…
Michael Everson
compare CJK in terminals; double the width of, e.g.,
> Latin characters).
Hm. Time for me to put VS support into Everson Mono, than, and see what
happens. But I think you’re probably right, though.
Tak for hjælpet.
Michael Everson
shapes is not grounds
for disunifying it” suggests an underlying view that "everything is already
encoded and additions are disunifications”. I do not subscribe to this view.
Michael Everson
ew decades at
> least), or decisions that at a minimum might be evaluated as "well, they
> didn't know better then", rather than as "they definitely should have known
> better, even then”.
Really, my practice when approaching this is the same as it has been for
additions to Latin or Greek or Cyrillic. I’m quite consistent. :-)
>> A proposal will be forthcoming. I want to thank several people who have
>> written to me privately supporting my position with regard to this topic on
>> this list. I can only say that supporting me in public is more useful than
>> supporting me in private.
>
> I'm looking forward to your proposal. I hope it clearly indicates why (you
> think) there's no danger of inconveniencing modern practitioners.
To be honest, we didn’t have to say “r rotunda will not affect modern users of
the Latin script”, now, did we? :-)
Today I received Ken’s book on the Deseret-script English-Hopi vocabulary. This
will help us move forward with a proposal.
Best,
Michael Everson
On 6 Apr 2017, at 13:19, Christoph Päper wrote:
>
> Although Michael Everson readily dismisses any connection to emojis, e.g.
> L2/16-021 or L2/16-087+088, and hence the Emoji and Emoji_Presentation
> character properties as well as sequences with variation selectors 15 and 16
Can you give an example of any font which has two glyphs in it for ß?
I mean, I was in Berlin and I took this picture:
http://evertype.com/standards/unicode-list/seydlitzstr.jpg
Do you think we should encode a Latin straight y (like the Cyrillic one) so we
can write Seүdlitzstraſʒe?
> On 6 Apr
On 6 Apr 2017, at 11:00, Christoph Päper wrote:
>
> Michael Everson :
>>
>> Standardized variation sequences are the best way to achieve this simply and
>> without needless duplication. :-)
>
> I still agree with this assertion.
So do I.. ;-)
>> Yes bu
ith other characters in the standard.
At some point this should be taken off the main list since discussion will get
very detailed very quickly.
Michael Everson
> On 6 Apr 2017, at 05:41, Richard Wordingham
> wrote:
>
> On Thu, 6 Apr 2017 01:11:09 +0100
> Michael Everson wrote:
>
>> On 5 Apr 2017, at 22:48, Richard Wordingham
>> wrote:
>>
>>> I tried to read it from UTS#51 ‘Unicode Emoji', which i
t ('foreground') on a blue background?"
Michael Everson
o-one insist on using it for terminal emulation).
Ha, so you’re saying it’s mostly for things like Everson Mono that it matters…
;-)
> All that is needed for that is a manoeuvre to copy a few glyphs within the
> font (when creating the font). I guess that is not very hard…
It is not.
Michael Everson
On 6 Apr 2017, at 01:54, Kent Karlsson wrote:
>>> - some bidi fix [preferably making the box/border drawing characters bidi
>>> "L", if possible; otherwise a caveat that if there is an expectation to
>>> paste in such a board into an RTL document, bidi controls need be used to
>>> LTR the boar
On 6 Apr 2017, at 01:53, Kent Karlsson wrote:
>
>> Oh, you misunderstood me. I knew it was raw HTML. I didn¹t expect it to
>> render. But it was meaningless code.
>
> It was a response to Marcus, in that HTML might be used (with existing
> characters and no VSs) to format chess boards. And he
:31, Kent Karlsson wrote:
>
>
> Exactly.
>
> /K
>
> Den 2017-04-06 01:25, skrev "Michael Everson" :
>
>> 2581 FE00; Chessboard box drawing; # LOWER ONE EIGHTH BLOCK
>> 258F FE00; Chessboard box drawing; # LEFT ONE EIGHTH BLOCK
>> 2594 FE00; C
cter shapes and just pasting in the chess
shapes to those code positions
Michael Everson
dots
have some of the dots red and some black.
Michael Everson
I agree with Rebecca. It’s going to be a handful of characters, used by the
handful of people who use legacy character sets. Those people exist (I run Mac
OS 9 regularly because it’s necessary for some of my work) and since some of
these legacy characters are encoded, it makes sense to make sure
n hieroglyphs!
Put it out of your mind.
Michael Everson
On 5 Apr 2017, at 22:13, Kent Karlsson wrote:
>
> Kent, I can’t read this in a plain-text e-mail.
>
> Well, it was SUPPOSED to be explicit HTML code in the email. It was NOT the
> intent that the given example was to be
> rendered directly in the email (even if you have HTML emails enab
and for its "White" Challenger), but making distinctions
> between horses (horses-dragoons) and cavalry. When promoting using chess
> pieces, the promotion may be shown by placing the chess piece.on top of a
> draught piece or coin/token. Coins/tokens are used to promote pawns (just
> stack two pieces like in draught game).
Shogi isn’t chess.
I thank Mr Verdy for his defence of my proposal.
Michael Everson
a CHESSPIECE ON A
> SQUARE, thus a change of meaning.
No, it’s not. CHESSPIECE is still CHESSPIECE. The glyph for CHESSPIECE needs to
be altered in order to make it suitable to use the characters in a way which
will permit the presentation and interchange of chessboard matrices.
Michael Everson
a
as in:
http://evertype.com/standards/unicode-list/34-variantim.png
and generate tables from it (if the narrative data were well-formed).
All the UTC has to do is approve the set of VS sequences as a *standardized*
way of doing this. Ad-hoc ligation is just going to lead to continued chaos, as
well as continued dependence on differently-encoded ASCII fonts.
Michael Everson
s (no VS) and get
> the same result when using a proper font.
No, because yours isn’t as well thought-out in terms of the structure of
plaintext chessboard data. (Probably only because I’ve been working on this
with real fonts for a good while now.) See my next e-mail.
Michael Everson
text like
http://evertype.com/standards/unicode-list/34-variantim.png
As I say, it’s *permissible* to have the unmodified chesspiece glyph be the
same as the white-square chesspiece glyph, but it’s not obligatory, and we must
preserve font designer choice here.
Michael Everson
ext colour in Quark XPress. It has nothing to do with the
proposal for variation sequences.
http://evertype.com/standards/unicode-list/looking-glass-yellow-blue.png
Michael Everson
Kent, I can’t read this in a plain-text e-mail. I can’t paste it into an
ordinary word-processor like Word as in my previous response to Markus, or in
Pages (left) or LibreOffice (right) as shown here. (I simply pasted in the text
from Word to each of those. It’s odd to see that there is some va
l send you the ttf of this one so
you can tinker with glyph placement as you wish, if the proposal is accepted
and the standardized variation sequences accepted.
Michael Everson
n actual problem?
>
> See above.
You failed to identify an actual problem with the proposal.
The actual problem is (1) chess fonts aren’t using unicode characters (2) VS
selectors can help provide a standardized way that enables chess fonts to do so
and (3) the proposal gives a mechanism for doing that which will work in
environments where VS substitution glyphs are supported.
Michael Everson
1 - 100 of 2428 matches
Mail list logo
