<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:x="urn:schemas-microsoft-com:office:excel" 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:"Angsana New";
panose-1:2 2 6 3 5 4 5 2 3 4;}
@font-face
{font-family:"Cordia New";
panose-1:2 11 3 4 2 2 2 2 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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
.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">Thanks, John<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As part of a separate issue that required touching the “Application interface” fields, I’ve drafted a revision for ‘lfbd’ and ‘rtbd’ to say the following:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">“In recommended usage, the application applies this feature automatically to characters at the right end of a horizontal line when the 'opbd' feature has been applied to those characters. See the the ['opbd'](#opbd) feature
for additional information.”<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">To allow for usage of ‘lfbd’ or ‘rtbd’ independent of ‘opbd’, I’ve have to revise that, but that would be doable.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Peter<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> mpeg-otspec <mpeg-otspec-bounces@lists.aau.at> <b>
On Behalf Of </b>John Hudson<br>
<b>Sent:</b> Wednesday, September 16, 2020 3:02 PM<br>
<b>To:</b> MPEG OT Spec list (mpeg-otspec@lists.aau.at) <mpeg-otspec@lists.aau.at><br>
<b>Subject:</b> Re: [MPEG-OTSPEC] 'opbd' feature<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 16092020 2:50 pm, Peter Constable wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Since Adobe had registered this feature, I asked them to investigate and come up with a recommendation. Sairus has just provided Adobe’s recommendation in the issue discussion:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> “<span style="font-size:10.5pt">Adobe would like ‘opbd’ and its minions ‘lfbd’ & ‘rtbd’ to be marked as deprecated in the features registry.</span>”<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> I’d like to hear from others if they would support or, at least, have no objection to these being marked as deprecated.<o:p></o:p></p>
</blockquote>
<p>I am 100% okay with opbd being deprecated.<o:p></o:p></p>
<p>The individual lfbd and rtbd features are, however, potentially useful without opbd if rewritten and, indeed, could constitute part of a model that might also involve tpbd (top) and (btbd) bottom optical bounds features for vertical text. The error of the
original feature registration was the idea that a single feature was needed to be able to apply the others, as a kind of gateway between application function and the individual features and their lookups. The idea of using GPOS to define margin alignment isn't
a terrible one in itself, especially for some scripts and styles that are not well served by algorithmic margin alignment such as currently available in InDesign.<o:p></o:p></p>
<p>That said, implementation of GPOS optical margin alignment, in both fonts and applications, requires some significant work, which I'm not holding my breath awaiting. I would rather, however, consider these features potential or pending, rather than deprecated.
It would be silly to formally deprecate them and then decide down the road that we'd actually like to use them.<o:p></o:p></p>
<p>JH<o:p></o:p></p>
<p><o:p> </o:p></p>
<pre>-- <o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>John Hudson<o:p></o:p></pre>
<pre>Tiro Typeworks Ltd <a href="https://eur05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.tiro.com%2F&data=02%7C01%7C%7Cc2f3ce5132c047fc3bfb08d85a8c3312%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637358905478869797&sdata=mQn9iiMB1WwQsuquVtGzDiXUQPEWgXdYVlHmevNnkDY%3D&reserved=0">www.tiro.com</a><o:p></o:p></pre>
<pre>Salish Sea, BC <a href="mailto:tiro@tiro.com">tiro@tiro.com</a><o:p></o:p></pre>
<pre><o:p> </o:p></pre>
<pre>NOTE: In the interests of productivity, I am currently <o:p></o:p></pre>
<pre>dealing with email on only two days per week, usually <o:p></o:p></pre>
<pre>Monday and Thursday unless this schedule is disrupted <o:p></o:p></pre>
<pre>by travel. If you need to contact me urgently, please <o:p></o:p></pre>
<pre>use some other method of communication. Thank you.<o:p></o:p></pre>
</div>
</body>
</html>