Am Tue, 24 Aug 2010 16:54:29 +0900 schrieb Andrew A. Adams: > Andy Lin wrote: >> Could it be possible you have two copies of IPAMincho in your >> system/texpath right now? This has been known to result in issues such >> as incorrect glyphs showing up in the output, as in your case. > > > The prize goes to Andy Lin for the simplest solution and the weirdest > behaviour of a program I've seen in a while. There were indeed three, not > just two, copies of the font on my system. I had one in my local .fonts > directory and removed that yesterday, but it didn't seem to help. Today I did > a check again and found that two copies were in separate subdirectories in > /usr/share/fonts (japanese and IPA). I deleted one of the two and > lo-and-behold, I get the attached pdf. > > Thank you all for your suggestions. Please remember this gotcha for anyone > having similar problems in future: do a search for the font file and delete > duplicates from anywhere XeTeX might find them, particularly from two places > in /usr/share/fonts.
There is no need to search your system. As I told you you can get the pathes of fonts involved in the log of xetex and the terminal output of xdvipdfmx: "Put \XeTeXtracingfonts=1 in your document and call xelatex with the option --output-driver="xdvipdfmx -vv"" -- Ulrike Fischer -------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
