<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 19 Jun 2008, at 1:09 pm, Apostolos Syropoulos wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">2008/6/19 Peter Heslin <<a href="mailto:p.j.heslin@durham.ac.uk">p.j.heslin@durham.ac.uk</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d"><br></div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I think that the correct level for this typographic practice to be<br> handled is in OpenType. I am no expert on it, but I imagine that it<br> should be possible for a font to provide mappings for text in small<br> caps and all caps that do away with accents for text set in these<br> typographic contexts.<br> </blockquote><div><br>Indeed this is a solution. But it is not backwards compatible.<br>I do not expect font companies to release new fonts fixing this<br>issue. In addition, this requires to be able to enable an OpenType <br> feature, something that cannot be done with the present version <br>of fontspec.</div></div></blockquote><br></div><div>Why not? Fontspec supports enabling arbitrary OpenType features.</div><div><br class="webkit-block-placeholder"></div><div>JK</div><div><br></div></body></html>