20

I updated my MiKTeX to the newest version a few days ago, and after this when I compile documents with the fontspec package included, there's a warning. For example:

\documentclass{article}
\usepackage{fontspec}

\setmainfont{Adobe Garamond Pro}

\begin{document}
  Hello, world!
\end{document}

Build Output shows:

*************************************************
* LaTeX warning: "xparse/redefine-command"
* 
* Redefining document command \oldstylenums with arg. spec. 'm' on line 107.
*************************************************

Why this happens? How to solve it?

4
  • 3
    It's simply an innocuous warning.
    – egreg
    Mar 3, 2012 at 23:36
  • @egreg: Should it really be a warning then? It can well confuse users. Mar 3, 2012 at 23:39
  • 1
    @Andrey: xparse raise a warning whenever one use \RenewDocumentCommand, since redefining a macro is always at some risk. There are also some other innocuous warnings, e.g. some of the font substitution warnings.
    – Leo Liu
    Mar 4, 2012 at 1:58
  • 5
    @LeoLiu: I understand that redefining macros has potential harm. But I believe that issuing a warning means requiring the user to take an action to fix this warning. Here we can take no action and no action is even required; we can't get rid of the warning (which means that now I can't tailor my document to not generate any warnings). Hence I think this should be an info, not a warning. Mar 4, 2012 at 7:31

1 Answer 1

11

It should be possible to silence this kind of messages via

\usepackage[log-declarations=false]{xparse}
\usepackage[quiet]{fontspec}

but the option to xparse is currently broken and has no effect. The version I'm referring is

xparse.sty 3471 2012-02-26

All these packages are quite new and developing, so warning messages can help debug problems. However, the message you're referring to is completely harmless.

4
  • 2
    The issue isn't in xparse per se but is to do with how (or indeed if) kernel-level messages are filtered out. There will be some update on this over the next week or so.
    – Joseph Wright
    Mar 4, 2012 at 10:20
  • 1
    This is still happening - I am very new to Latex, like 1 day, and I agree with comments above - Why warn about something the user has no way of fixing!? Now do I read every warning and try to work out what is important and what is not!? Or do I just ignore ALL Warnings and not try to understand what is going on with them .... Confused newbie!
    – user35378
    Aug 19, 2013 at 19:25
  • @user35378 -- xparse is easier to program than the corresponding latex 2e stuff, but it remains experimental. if you're a 1-day-old latex programmer, you were badly advised: far better to use "standard" stuff than to use stuff that is still in development, in your situation. ... imho. Oct 16, 2013 at 14:57
  • @wasteofspace I believe that user35378 is complaining that fontspec is still issuing the warning. The solution, of course, is to update the TeX distribution.
    – egreg
    Oct 16, 2013 at 15:01

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .