<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@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;}
@font-face
{font-family:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">On Saturday, October 3, 2020 6:06 AM MURATA Makoto wrote:<br>
<br>
</span><o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">We need courage to state principles. Otherwise,<br>
nothing will change.<br>
<br>
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">We also need to be honest, especially when it comes to getting something done.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
Font shaping for developing countries appears to<br>
require significant enhancements to fonts. Requests<br>
from CSS also require a lot of work. I do not believe<br>
that such enhancements can be done by private<br>
companies, which have to care how much investment<br>
is required and how much profit can be expected.<br>
<br>
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Let us be realistic about how the work is done and who does it. Standards organizations, be it W3C or ISO, don’t do the work in a vacuum, the specs (CSS, OFF,
…) don’t come out of thin air. These organizations exist only because of [and for] their members – both public and private companies, who make significant contributions investing time, money, and resources to send their experts to work collaboratively to get
things done. These investments are substantial, and participating member companies have to remain profitable to cover their expenses. They may not profit directly from standards work, but they do need to profit from it one way or another, or nothing gets done.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
Therefore I do not think that we should agree to tie<br>
our hands.<br>
<br>
<span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Who are “we” who shouldn’t agree to tie our hands? Who do you think will do this work (and implement the results!) if private companies walk away from it? Who
has resources to get things done when “</span>Font shaping for developing countries appears to require significant enhancements to fonts<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">”?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Vlad<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><br>
Regards,<br>
Makoto<br>
<br>
2020<span style="font-family:"MS Gothic",serif">年</span>10<span style="font-family:"MS Gothic",serif">月</span>3<span style="font-family:"MS Gothic",serif">日</span>(<span style="font-family:"MS Gothic",serif">土</span>) 17:55 Caleb Maclennan <<a href="mailto:caleb@alerque.com">caleb@alerque.com</a>>:<br>
><br>
> On Sat, Oct 3, 2020 at 1:23 AM MURATA Makoto <<a href="mailto:eb2m-mrt@asahi-net.or.jp">eb2m-mrt@asahi-net.or.jp</a>> wrote:<br>
> > I think that synchronization with OT should not be mentioned in<br>
> > this AHG.<br>
><br>
> Why not? It seems quite relevant to me. Even if I don't *like* the<br>
> current process and the black-box stages it involves, the current<br>
> defacto way the MOFF (MPEG Open Font Format) spec actually gets<br>
> updated is through tracking changes to MSOT (Microsoft OpenType).<br>
> They are still (rightfully) in a position to do whatever they want<br>
> with their own spec for internal use and pragmatically speaking the<br>
> most effective way we have to get things fixed in OFF is by appealing<br>
> to M$ as a benevolant dictator that can actually change their own<br>
> spec and pretty significant weight to get their changes rubber<br>
> stamped into OFF (since keeping them in sync is kind of the deal).<br>
><br>
> However bad this state of affairs is and however silly it is for M$<br>
> to try to keep their cake and eat it too — as long as this is the<br>
> state of things I'd much rather hear about work they are doing<br>
> internally on their MSOT spec through this AHG than have the topic<br>
> be made off limits. The inevitable result of that would be for the<br>
> entire end-to-end process to happen in closed groups that many in<br>
> the industry don't have access to even audit!<br>
><br>
> In short it seems very relevant to me for the sync process from<br>
> MSOT→OFF to be mentioned in this AHG list. Even if some of the<br>
> steps are still off limits to plebians, the fact that some of the<br>
> steps are closed doesn't seem like a good reason to close off all<br>
> of the process.<br>
><br>
> Why do you think the OT→OFF synchronization that is both currently<br>
> and historically a significant part of what the OFF is should be<br>
> off limits for disccussion in this AHG?<br>
><br>
> Caleb<br>
> _______________________________________________<br>
> mpeg-otspec mailing list<br>
> <a href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a><br>
> <a href="https://protect-us.mimecast.com/s/fzBxC2kor7tkEOQQT1t6e5">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><br>
<br>
<br>
<br>
-- <br>
Regards,<br>
Makoto<br>
_______________________________________________<br>
mpeg-otspec mailing list<br>
<a href="mailto:mpeg-otspec@lists.aau.at">mpeg-otspec@lists.aau.at</a><br>
<a href="https://protect-us.mimecast.com/s/fzBxC2kor7tkEOQQT1t6e5">https://lists.aau.at/mailman/listinfo/mpeg-otspec</a><o:p></o:p></p>
</div>
</body>
</html>