>> > I have had problems like this as well, a while ago, but simply with >> > fontspec. I had one of Adobe's fonts in both my windows fonts >> > directory and in the TeX tree (same version btw) and my documents came >> > out all garbled. Removing the one in windows\fonts fixed it. >> > >> > Should XeTeX just stick with whichever of the fonts it finds first? >> >> I'm not sure, but it may be that the font file used by xetex is not the >> one xdvipdfmx is graping glyphs from, I don't know how xetex passes the >> font to the xdv file, but may there are two separate font lookup >> routines and each one is returning a different font file? Checking the >> source code might help, but I don't feel like doing it. > > Looking further, it seems that when a system font is used, xetex embeds > the font name not the resolved path in the xdv file, so xdvipdfmx has to > lookup the font again and it seems to find a different font sometimes. I > don't know why xetex don't just embed the resolved full path of the > font, as it does already with with "external fonts", this makes sure > xdvipdfmx is getting the same font file as xetex and alleviate the need > of font lookup logic in xdvipdfmx itself. May be there is some > (historical?) reason, but judging by how popular this issue, I think it > might be reasonable to consider this. > > Regards, > Khaled
Khaled seems to have pinpointed the common source of all of these troubles with garbled PDF files. I hope that now somebody contacts Jonathan Kew about it. Mariusz Wodzicki -------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
