<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On 22 Sep 2006, at 5:15 pm, Steve Grathwohl wrote:</DIV><BLOCKQUOTE type="cite"><DIV><DIV><FONT class="Apple-style-span" color="#000000"><BR class="khtml-block-placeholder"></FONT></DIV><DIV>OK, speaking of Juncode...<BR><BR>if I say <BR><BR>\documentclass{article}<BR>\usepackage{fontspec}<BR>\setromanfont{Junicode}<BR><BR>\begin{document}<BR>\textsc{first}<BR>\end{document}<BR><BR>I get fiRST; that is, lowercase fi lig then smallcap RST. What's going on here? I haven't seen this behavior in any other font. <BR></DIV></DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>This indicates that the lookups are incorrectly ordered in the font. You should report this as a bug to the font developer. You'll see the same effect if you use it in TextEdit, for example (where you can access the Small Capitals feature via the Typography palette).</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>XeTeX is simply applying the lookups in the order they're found in the font, which is what the OpenType spec says to do (though some applications may override the order and thus mask the error). So if the lookup that implements the "fi" ligature comes before the one that maps lowercase letters to small caps, you'll see a result like this.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><BLOCKQUOTE type="cite"><DIV><DIV>For the record, my XeTeX is getting a bit gamey (version .995 for Windows, grabbed late July; will upgrade RSN).<BR></DIV></DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Upgrading is good :) ... but I don't think it will have any effect on this issue. There have been some bug-fixes since July, but unless you're affected by those specific bugs, you won't notice anything.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>JK</DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR></DIV><BR></BODY></HTML>