<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
BTW, Adobe is aware of the problem. It's unlikely that they will fix it
in the existing fonts, except by perhaps providing an alternate glyph
which has different kerning, but in the most recent fonts (Hypatia Sans
Pro, Arno Pro), they have taken a different approach on this particular
kerning issue. <br>
<br>
If you want to avoid conflicts, you can always rename the entire font.
After dumping the OTF into XML using FontTools/TTX, you can safely do a
global search-replace from "Minion" to "MinionWas" or something like
that. <br>
<br>
Best,<br>
Adam<br>
<br>
<br>
John Was wrote:
<blockquote cite="mid:002b01c8a163$3d161230$0200a8c0@keith" type="cite"><DEFANGED_META
http-equiv="Content-Type" content="text/html;charset=UTF-8">
<DEFANGED_META content="MSHTML 6.00.6000.16640" name="GENERATOR">
<style></style></DEFANGED_META></DEFANGED_META>
<div><font face="Arial Unicode MS">Dear Adam</font></div>
<div> </div>
<div><font face="Arial Unicode MS">Thanks for that - it's a very neat
solution. I was trying to keep away from working on the font itself
since so many OTF fonts are under development and it would be necessary
to keep track of what one had done with version A when installing an
updated version B - hence the desire to specify kerning pairs in a
user-generated list which could easily be called up and tinkered with
as a separate entity. But for the moment I'm happy with any solution
that will avoid the squashed appearance of e.g. L'espace or etc.'.</font></div>
<div> </div>
<div><font face="Arial Unicode MS">Best</font></div>
<div> </div>
<div> </div>
<div><font face="Arial Unicode MS">John</font></div>
<div> </div>
<div> </div>
<div>----- Original Message ----- </div>
<blockquote
style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">
<div
style="background: rgb(228, 228, 228) none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial; font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>From:</b>
<a moz-do-not-send="true" title="list.adam@twardoch.com"
href="mailto:list.adam@twardoch.com">Adam Twardoch</a> </div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>To:</b>
<a moz-do-not-send="true" title="xetex@tug.org"
href="mailto:xetex@tug.org">Unicode-based TeX for Mac OS X and other
platforms</a> </div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>Sent:</b>
Friday, April 18, 2008 2:06 PM</div>
<div
style="font-family: arial; font-style: normal; font-variant: normal; font-weight: normal; font-size: 10pt; line-height: normal; font-size-adjust: none; font-stretch: normal;"><b>Subject:</b>
JunkEmail: Re: [XeTeX] Kerning support</div>
<div><br>
</div>
Changing one or two kerning pair values in your own local copies of a
font is trivial using <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.font.org/software/ttx/">http://www.font.org/software/ttx/</a><br>
(just convert the font to XML, change the values using a text editor
and convert the font back to OTF). The license agreement for Adobe
fonts allows that. <br>
<br>
A.<br>
<br>
<br>
Will Robertson wrote:
<blockquote
cite="mid:D03C1243-216E-4953-92D7-28E23A856F10@gmail.com" type="cite">On
17/04/2008, at 6:43 PM, John Was wrote: <br>
<blockquote type="cite">I think intercharacter tokens could be
problematic <br>
</blockquote>
<br>
Yeah; as Jonathan pointed out to me when this feature was first
introduced, interchar tokens are inserted regardless of the font; it
would be possible to detect the font and conditionally insert the
kerning, but that would mess up other uses for the interchar feature
(namely, detecting when a certain script changes). <br>
<br>
So while you could do it for an ad hoc purpose, it's really not the way
to go :) <br>
<br>
Will<br>
<pre wrap=""><hr size="4" width="90%">
_______________________________________________
XeTeX mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:postmaster@tug.org">postmaster@tug.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://tug.org/mailman/listinfo/xetex">http://tug.org/mailman/listinfo/xetex</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Adam Twardoch
| Language Typography Unicode Fonts OpenType
| twardoch.com | silesian.com | fontlab.net
</pre>
<p> </p>
<hr> _______________________________________________<br>
XeTeX mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:postmaster@tug.org">postmaster@tug.org</a><br>
<a class="moz-txt-link-freetext" href="http://tug.org/mailman/listinfo/xetex">http://tug.org/mailman/listinfo/xetex</a><br>
</blockquote>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
XeTeX mailing list
<a class="moz-txt-link-abbreviated" href="mailto:postmaster@tug.org">postmaster@tug.org</a>
<a class="moz-txt-link-freetext" href="http://tug.org/mailman/listinfo/xetex">http://tug.org/mailman/listinfo/xetex</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Adam Twardoch
| Language Typography Unicode Fonts OpenType
| twardoch.com | silesian.com | fontlab.net
</pre>
</body>
</html>