[XeTeX] Page Number Font Issue

2011-01-06 Thread William Voelker
Greetings, I have an page numbering issue in a longer document I'm working on. Three pages have their numbers appear incorrectly; two are italicized, but are in the same font as the body font for the rest of the document, while one appears in a secondary font in which text is set going across a

Re: [XeTeX] Page Number Font Issue

2011-01-06 Thread William Voelker
Thank you for the response. Here's a link to a sample file (it's a bit long for the mailing list): http://voelker.wordpress.com/2011/01/06/xetex-problem/ I did notice two things in paring down the header (to see what did and did not make a difference). Removing the Geometry package + commands a

Re: [XeTeX] Page Number Font Issue

2011-01-06 Thread William Voelker
Thanks to all who answered on this question; your answers helped me clear up the problems I was having. As it turns out, I made some of these foolish errors (redefining via \setromanfont repeatedly, for instance) because one of the first fonts I'd tried for the project didn't automatically use b

[XeTeX] Font Location Issue?

2013-07-24 Thread William Voelker
Greetings, I recently upgraded my Mountain Lion system to the MacTex 2013 distribution, and eliminated the older distributions I had previously installed ('10, '11, '12). Here's my problem: while everything else I've thrown at '13 has worked just fine, it simply refuses to use one particular f

Re: [XeTeX] Font Location Issue?

2013-07-24 Thread William Voelker
Thanks for all the comments. A couple notes: 1. I've worked around this, and simply substituted another font (for now, at least). 2. Stone Sans worked just fine before I installed MacTex 2013; it also works in TextEdit, for instance, and shows up in Font Book (and validated without issue). Writ

[XeTeX] MatchUppercase / Lowercase not working

2014-07-13 Thread William Voelker
Since I've updated to TeXLive 2014 (Mavericks), a command such as this \fontspec[Scale=MatchUppercase]{Optima} returns an "Undefined control sequence" error. Has there been a change to fontspec? Files I used this command with in 2013 (and before) sailed through without a hiccup. Wm

Re: [XeTeX] MatchUppercase / Lowercase not working

2014-07-14 Thread William Voelker
On Jul 13, 2014, at 8:05 PM, Herbert Schulz wrote: > >> Since I've updated to TeXLive 2014 (Mavericks), a command such as this >> >> \fontspec[Scale=MatchUppercase]{Optima} >> >> returns an "Undefined control sequence" error. Has there been a change to >> fontspec? Files I used this comma