Tell me more ×
TeX - LaTeX Stack Exchange is a question and answer site for users of TeX, LaTeX, ConTeXt, and related typesetting systems. It's 100% free, no registration required.
up vote 13 down vote favorite
3

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?

share|improve this question
3  
It's simply an innocuous warning. – egreg Mar 3 '12 at 23:36
@egreg: Should it really be a warning then? It can well confuse users. – Andrey Vihrov Mar 3 '12 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 '12 at 1:58
2  
@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. – Andrey Vihrov Mar 4 '12 at 7:31

1 Answer

up vote 6 down vote accepted

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.

share|improve this answer
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 '12 at 10:20

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.