Jean-Marc Lasgouttes wrote:
> I am not sure I understand. I thought the problem was that beamer
> loads xcolor by itself. In this case, what is the difference between
> \PassOptionToPackage{usenames}{color}
> \usepackage{color}
> and
> \usepackage[usenames]{color}Beamer apparently loads color. Either color and xcolor are loaded by beamer, or xcolor pretends that it is color. Anyway, here's the relevant LaTeX error: The package color has already been loaded with options: [pdftex] There has now been an attempt to load it with options [usenames] Adding the global options: pdftex,usenames to your \documentclass declaration may fix this. Try typing <return> to proceed. The difference is, of course, that the new version does not lead to option conflicts. > And what is the result? Is the usenames option really active when > using beamer+changes? Why? I'm not sure either. However, at least change tracking marks are visible in the DVI output of beamer documents.* To be sure that usenames is active, \PassOptionsToPackage would have to be placed before \documentclass. Something for post-1.4.0 IMHO. *My theory is that usenames is not active in Beamer. But usenames is declared obsolete in the xcolor docs. So obviously that option is not needed anymore when using dvipost together with xcolor. > I am sorry to ask again, it may be I did not follow this thread > closely enough. Feel free to ask further questions. Jürgen
