Hi Wilfred: Thanks for your reply. The problem I had was that in /usr/local/share/fonts, I had Officina as a TTF and a OTF file, I removed the TTF file and I get correct results, ie the same font ini two different formats.
Thanks for your help, Kind Regards, Alan On Sat, Jul 10, 2010 at 4:48 AM, Wilfred van Rooijen <wvanrooi...@yahoo.com>wrote: > But what do you mean by "it does work and does not work"? If it used to > work, then it should still work ;-)). Can you send some more info about what > goes wrong and where, and maybe an example input file? > > Wilfred > > --- On *Sat, 10/7/10, Alan Jones <ajones...@gmail.com>* wrote: > > > From: Alan Jones <ajones...@gmail.com> > Subject: Re: [XeTeX] Unable to use XeLaTeX correctly upon TexLive2008 > Install > To: "Unicode-based TeX for Mac OS X and other platforms" <xetex@tug.org> > Date: Saturday, 10 July, 2010, 12:52 AM > > > Hi Wilfred Thanks: > > It works and it does not work on several fonts for me. I have been using > > otfinfo -a fontname.otf > > and > otfinfo -p fontname.otf > > to get the font name for setting /fontspec command. > > Kind Regards, > Alan > > On Fri, Jul 9, 2010 at 1:10 PM, Wilfred van Rooijen > <wvanrooi...@yahoo.com<http://mc/compose?to=wvanrooi...@yahoo.com> > > wrote: > >> Hi, >> >> The error indicates that the particular font is not found as part of the >> system-wide fonts. Then, xelatex tries to generate the font in the >> old-fashioned way, and this fails. This means that you are using the wrong >> name in the \fontspec command. On Linux, do: >> >> 1. run "fc-cache -fv" >> >> This will regenerate the cache of system-wide fonts. You should see your >> font directory in the output. If not, that means that the font directory is >> skipped. In that case, you need to instruct fc-cache to include your >> directory in the font cache. >> >> 2. run "fc-list" >> >> This gives a list of all recognized fonts as cached by fc-cache. Note that >> the name given in this list is the name you should use in the \fontspec >> command. The name in the font cache may be different from the filename of >> the corresponding OTF file. >> >> The OTF fonts have several "identification strings", which may or may not >> be the same as the filename. If you really cannot get xelatex to recognize >> the font name, you can open the OTF file in fontconfig and look for the >> identification strings and try which one is correct to load the font. >> >> HTH, >> Wilfred >> >> >> >> >> -------------------------------------------------- >> Subscriptions, Archive, and List information, etc.: >> http://tug.org/mailman/listinfo/xetex >> >> > > -----Inline Attachment Follows----- > > > > > -------------------------------------------------- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > > > > > > -------------------------------------------------- > Subscriptions, Archive, and List information, etc.: > http://tug.org/mailman/listinfo/xetex > >
-------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex
