<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi Mark-Jan<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We’ve been talking about plain text on and off for over 18 months so I was interested to read your L2/16-177 “new system” earlier this month and your latest update yesterday (<a href="https://mjn.host.cs.st-andrews.ac.uk/tmp/unicode2.pdf">https://mjn.host.cs.st-andrews.ac.uk/tmp/unicode2.pdf</a>). Good to see your number of control characters now reduced, more consideration has been given to OpenType and some discussion in Cambridge has been factored in. I understand what you are trying to do and there are points I’d like to discuss when we have time. There are items you note that indeed need to be progressed and agreed (EMPTY, STACK CARTOUCHE …)<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>However I am disappointed you have not taken on board the fundamental failing with the scheme you’ve been developing that makes it unsuitable for Unicode plain text consideration, however useful it may be for other purposes. I thought this was clear at Cambridge but apparently not.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Unicode plain text hieroglyphic is exposed to a huge audience and the very first consideration is <u>don’t make simple things complicated</u>. Use of BEGIN/END for every group breaks that basic rule. Your scheme is unnecessarily complicated so fails at the outset. It’s a continuing distraction for the less technically minded in this group to continue to hold it up as a viable alternative to the current UTC recommendation. It is not.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>MdC X1:R1 in your scheme uses <u>3 control characters</u>. Quite honestly I find it hard to understand why anyone thinks this is possibly a good idea. <u>If anyone reading this does support 3 over 1 please let me know your reasoning I’m actually quite curious why I’ve had to spend time on this.<o:p></o:p></u></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What you’ve tried to do is build a theoretical model which describes cluster layout given a set of constraints and that’s all good as an academic exercise. I’d be interested to see it tested against texts and data. All features of could be added in some way to the three control system as HLP or extra controls. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So, there’s no need to throw your work away. Some parts apply to plain text implementation e.g. your description on making an MdC-like font. Plenty more you could re-purpose should you wish to continue to be involved in Unicode developments.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>What I suggest you do is consider how you might use elements of your scheme in a simple higher level protocol on top of plain text as it is at present (I’ll be circulating my considered view on adding to the 3 control set on Tuesday). Brackets in an HLP could be ok for rare cases. May be useful for TLA and Ramses. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Meanwhile if you have any ideas on how you would like to see e.g. 4 corners added to the existing proposal I’d be pleased to hear from your or anyone else on the topic.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Regards,<o:p></o:p></p><p class=MsoNormal>Bob<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>