<!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">
<div class="moz-text-flowed" style="font-size: 16px;" lang="x-unicode">Yves
Codet wrote:
<br>
<br>
<blockquote type="cite" style="color: rgb(0, 153, 0);">As Peter said
xltxtra loads fontspec, so you can only load the first one.
<br>
</blockquote>
<br>
Not too long ago, when I first learned about how xltxtra loads fontspec
<i class="moz-txt-slash"><span class="moz-txt-tag">/</span>and<span
class="moz-txt-tag">/</span></i> xunicode, I changed how my Syriac
.sty file loads fontspec, so that instead of
<br>
<br>
\usepackage{fontspec, xltxtra, xunicode}
<br>
<br>
I loaded only
<br>
<br>
\usepackage{xltxtra}
<br>
<br>
since it requires the other 2.
<br>
<br>
<b class="moz-txt-star"><span class="moz-txt-tag">*</span>But<span
class="moz-txt-tag">*</span></b>, the .sty file didn't know what to do
with the Syriac if I didn't <b class="moz-txt-star"><span
class="moz-txt-tag">*</span>explicitly<span class="moz-txt-tag">*</span></b>
load fontspec, i.e., all the Syriac glyphs became question marks from
the Syriac font, not only in the document loading the .sty file, but
even in the .sty file itself. Actually, I didn't experiment enough to
find out if it was fontspec or xunicode that was required, since the
Syriac glyphs are in another area of the font. Someone else might
verify how that works. (The font is Serto Jerusalem, one of the Meltho
fonts available from bethmardutho.org ).
<br>
<br>
So, maybe if you need to access a special section of a unicode font, it
might be best to load all three explicitly.
<br>
<br>
</div>
<pre class="moz-signature" cols="72">--
United in adoration of Jesus,
fr. michael gilmary, mma
Most Holy Trinity Monastery
67 Dugway Road
Petersham, MA 01366-9725</pre>
</body>
</html>