Proposal to add standardized variation sequences for chess notation

[Michael Everson]

On 3 Apr 2017, at 18:51, Markus Scherer <markus.icu at gmail.com> 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. 

This is plain text:
▗▁▁▁▁▁▁▁▁▖
▕□︀▨︁□︀▨︁□︀▨︁♞︀▨︁▏
▕▨︁□︀▨︁□︀▨︁□︀▨︁□︀▏
▕□︀▨︁♔︀▨︁□︀▨︁□︀▨︁▏
▕▨︁□︀▨︁□︀▨︁♘︀▨︁□︀▏
▕□︀▨︁□︀▨︁♚︀▨︁□︀▨︁▏
▕▨︁□︀▨︁□︀▨︁□︀▨︁□︀▏
▕□︀▨︁□︀♙︁♛︀▨︁□︀▨︁▏
▕▨︁□︀♕︁□︀▨︁♖︀▨︁□︀▏
▝▔▔▔▔▔▔▔▔▘

I can read this in my plain-text e-mail. I can copy it from the plain-text e-mail and past it into Quark XPress as in the proposal, or into Microsoft Word v. 15 for Mac as shown below (the first one is just as-is pasted into Word; the second formatted itself when I selected the Ludus font. None of these examples uses HTML. None uses some external folder with hard-to-format css rules. None needs to be constructed by some HTML or XML <table> matrix. It’s all just a font with normal OpenType features, and normal use of variation sequences. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://unicode.org/pipermail/unicode/attachments/20170403/6a493210/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ms-word-lg.png
Type: image/png
Size: 101582 bytes
Desc: not available
URL: <http://unicode.org/pipermail/unicode/attachments/20170403/6a493210/attachment-0001.png>