<div dir="ltr">Thanks all for the helpful replies. Previously I had a pfb version under TEXMFHOME dir<br>after removing it the problem seems to persist. I generated the pfb version so I can test<br>the font with plain pdfTeX engine. Do I have to remove all the other tfm, enc, map files also?<br>
I will give it a try ...<br><br>Kindest Regards,<br>Abdulrahman<br><br><div class="gmail_quote">On 27 June 2010 06:58, Jonathan Kew <span dir="ltr"><<a href="mailto:jfkthame@googlemail.com">jfkthame@googlemail.com</a>></span> wrote:<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="im">On 26 Jun 2010, at 16:46, Khaled Hosny wrote:<br>
<br>
> On Sat, Jun 26, 2010 at 03:04:05PM -0700, <a href="mailto:wodzicki@math.berkeley.edu">wodzicki@math.berkeley.edu</a> wrote:<br>
>><br>
>>> My guess is that you have an old version of the font installed somewhere.<br>
>>> Having to different version of the same font installed is known to cause<br>
>>> this kind of issues with xetex, deleting the old version(s) is enough<br>
>>> to solve this issue.<br>
>>><br>
>>> Regards,<br>
>>> Khaled<br>
>><br>
>> "an old version" should not be understood literally. Two identical copies<br>
>> of the exactly same font: one, say, in the system fonts directory, and<br>
>> another one in the TeX distribution tree -- will cause this behavior.<br>
<br>
</div>I have not seen any evidence that this is so, and would be very surprised if this happens.<br>
<div class="im"><br>
>> This<br>
>> is a very frustrating and well attested bug in XeTeX (which for some<br>
>> reason has been ignored so far by the XeTeX creator and maintainer).<br>
><br>
> Theoretically, if my previous "analysis" of this issue was correct, two<br>
> identical copies should not cause any problems, since both will have<br>
> the same glyph IDs. I should have said a different instead of old copy,<br>
> though.<br>
<br>
</div>Indeed. The problem may occur if two *different* versions of the "same" font (i.e., with the same font names, but different versions or different formats -- e.g., type 1 vs truetype) are installed. As I believe I have explained previously, it's possible that xetex will find one font during formatting, but then xdvipdfmx finds the other at PDF generation time, and the glyph IDs don't match.<br>
<br>
Obviously, it would be better if the two programs were guaranteed to always find the same font for a given name, but ensuring this for all configurations and environments may not be as simple as it sounds. For now, at least, the *strong* recommendation is to have only ONE version of any given font installed.<br>
<font color="#888888"><br>
JK<br>
</font><div><div></div><div class="h5"><br>
<br>
<br>
<br>
--------------------------------------------------<br>
Subscriptions, Archive, and List information, etc.:<br>
<a href="http://tug.org/mailman/listinfo/xetex" target="_blank">http://tug.org/mailman/listinfo/xetex</a><br>
</div></div></blockquote></div><br><br clear="all"><br>
</div>