<div class="gmail_quote">On Tue, Aug 24, 2010 at 10:58 PM, David Perry <span dir="ltr"><<a href="mailto:hospes.primus@verizon.net">hospes.primus@verizon.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
<br>
On 8/24/2010 8:17 PM, Gareth Hughes wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The fontspec manual discusses the difference between ICU and AAT font<br>
handling. Macs use the latter, Linux and other operating systems use the<br>
former.<br>
</blockquote></div>
This is true, but remember that OS X can also use Windows-style TrueType or OpenType fonts with no problem for standard scripts. In 10.4 Apple added support for OpenType Arabic, but not for Hebrew (as far as I know).<br>
<br>
So if you are using, e.g., the SBL Hebrew font (which doesn't come in a native AAT version) you would need to declare the script in order to activate the ICU renderer and get support for mark positioning via the OT features built into the font, whereas you wouldn't do so when working with a native AAT font.<br>
</blockquote><div><br></div><div>Yes, I had to learn this by experience. I need source files that work on all three major OSes, so I always specify font options. </div></div><div><br></div><div>You would think that OS X would grok ICU by now. Grrr!</div>
<br>Kirk<br>--<br>Kirk E. Lowery, PhD<br>President & Senior Research Fellow<br>The J. Alan Groves Center for Advanced Biblical Research<br>--<br>$DO || ! $DO ; try<br>try: command not found<br><br>