Colors by names using xcolor, LaTeX Error: Option clash for package xcolor.

Cisoto · September 21, 2020, 11:47pm

For some reason, I am not able to knit a very simple Rmd file if I use \usepackage[x11names]{xcolor}.
It pops up the message "LaTeX Error: Option clash for package xcolor".
All LaTeX functions works properly. Except this one.
I can work without options, but the color palette is so minimal, that the feeling of documents are very basic. Or I can work with a lot of code to define colors, but I need to work, not to code.
The next code is the minimum expression of my problem. A simple thing like try to change a font color is a nightmare.
The Azure1 color (at the bottom of the code) belongs to the color namespace x11names in xcolor.
If I change it to something basic like gray it will work ONLY if I delete the [option] part in xcolor package.

I am not expert at all. The answer may be too easy, but not for me.
I really need some solution.

I've had tried using \PassOptionsToPackage{x11names}{xcolor}: Same problem
I did reinstall FULL tinytext,

tinytex::reinstall_tinytex(): Same problem

I did reinstall TeX Live in my Linux.: Same problem (...and a lot of time and resources)
I did reinstall (afterwards) kableExtra, Knitr, Rmarkdown... and nothing seems to work.

Here is my Rmd example (just the problem)

---
always_allow_html: true
output:
   pdf_document
header-includes:
   \usepackage[x11names]{xcolor} 
   \usepackage{pifont}
   \usepackage[T1]{fontenc}
   \usepackage{anyfontsize}
   \usepackage{inputenc}
 ---

knitr::opts_chunk$set(echo = FALSE, warning=FALSE, error=FALSE)

 ```{r librerias, include = FALSE}  
 library(formattable)
 library(rmarkdown)
 library(tidyverse)
 library(kableExtra)
 library(latexpdf)
 library(tinytex)
 library(data.table)```

 \ding{32}
 \vspace{80mm}
 
 **\fontsize{28}{28}\selectfont Changing size works.**\newline
 
 \fontsize{20}{20}\selectfont Up or \fontsize{8}{8}\selectfont down.\newline
 
 \normalsize
 The next text will have a color change **\textcolor{blue}{LIKE THIS}**, or like **\textcolor{purple}{THIS}** and finally as **\textcolor{red}{THIS ONE}** ...something else.\newline
 
 
 A very simple table
 
 \LARGE Sampling
 \large


 ```{r }
 tracing <- data.table(X=c(1:10), Y=c(LETTERS[1:10]))
 kable(tracing, "latex") %>%
   kable_styling(
    position = "center",
     font_size = 8,
     full_width = FALSE,
     repeat_header_continued = FALSE,
     latex_options = "striped",
     stripe_color = "Azure1"
   ) ```

I am woking over RStudio-server.
I am on your hands.
Thank you so much for your time to solve such a problem to me.

R:

> version
               _                           
platform       x86_64-pc-linux-gnu         
arch           x86_64                      
os             linux-gnu                   
system         x86_64, linux-gnu           
status                                     
major          4                           
minor          0.2                         
year           2020                        
month          06                          
day            22                          
svn rev        78730                       
language       R                           
version.string R version 4.0.2 (2020-06-22)
nickname       Taking Off Again

Rstudio version:

$mode
[1] "server"

$version
[1] ‘1.3.1073’

$release_name
[1] "Giant Goldenrod"

EDIT:
If I use this code, I can verify some things.

The next text will have a color change **\textcolor[rgb]{0,.7,.3}{LIKE THIS}**, 
or like **\textcolor{Azure1}{THIS}** 
and finally as **\textcolor{red}{THIS ONE}** ...something else.\newline

The xcolor package is OK. I can use the [rgb] option in the \textcolor, without problem, but it is not possible to use the Azure1, whose definition is inside x11names. I can not use either another name space declared on the options given to xcolor in the header, it is not something specific to x11names.

cderv · September 22, 2020, 8:08am

This should work. You need to use that because pandoc latex template already use xcolor.

In this minimal reprex it does.

---
output:
   pdf_document
header-includes:
   - \PassOptionsToPackage{x11names}{xcolor} 
---
 
The next text will have a color change **\textcolor{blue}{LIKE THIS}**, or like **\textcolor{purple}{THIS}** and finally as **\textcolor{red}{THIS ONE}** ...something else.

Cisoto · September 22, 2020, 11:54am

Thank You Christophe...
Your work has been considered around this problem.
Your suggestion should work, but it don't.
In this code it works, because the colors in this particular fragment are the basic ones, but if I try with Azure1, or any other color in the x11names space, it displays:

output file: M_T2.knit.md

! Package xcolor Error: Undefined color `Azure1'.

I have had added new code at the end of the original post. It has r.g.b. definition (OK) and the color Azure1 (!Ok)

cderv · September 22, 2020, 1:12pm

Ok I see. This is currently something that pandoc does not handle because it loads xcolor with no option before the preamble, that is why it does not work.

See

github.com/jgm/pandoc

Missing xcolor names

opened 03:05AM - 12 Jul 20 UTC

closed 02:35PM - 06 May 21 UTC

krlmlr

format:LaTeX templates

xcolor names are a source of pain, because the LaTeX template loads `xcolor` bef…ore evaluating `header-includes`, and it seems impossible to load default color names after `xcolor` is loaded -- AFAICT it only supports the option interface, there's no command to load the default color sets. Can we unconditionally include ```tex \PassOptionsToPackage{dvipsnames,svgnames*,x11names*}{xcolor} ``` in the default LaTeX template, and perhaps add additional customization points that are evaluated at the beginning of the document and right after `\documentclass{}`?

and

github.com/jgm/pandoc

svgnames and x11names not supported for xcolor color names

opened 09:31PM - 03 Feb 20 UTC

closed 03:22PM - 10 May 21 UTC

noraj

format:LaTeX writer templates

svgnames and x11names not supported for xcolor color names. Despite of the do…cumentation saying it should: ![image](https://user-images.githubusercontent.com/16578570/73616745-a08cde00-4617-11ea-93ad-dccf5b9ca192.png) ## dvipsnames ``` $ pandoc basic-example.md \ --from markdown \ --to pdf \ -o bug.pdf \ --pdf-engine=pdflatex ``` ```markdown --- urlcolor: "RedOrange" --- [link](http://example.org) ``` ## svgnames ``` $ pandoc basic-example.md \ --from markdown \ --to pdf \ -o bug.pdf \ --pdf-engine=pdflatex Error producing PDF. ! Package xcolor Error: Undefined color `DarkOrange'. See the xcolor package documentation for explanation. Type H <return> for immediate help. ... l.56 \href{http://example.org}{link} ``` ```markdown --- urlcolor: "DarkOrange" --- [link](http://example.org) ``` ## x11names ``` $ pandoc basic-example.md \ --from markdown \ --to pdf \ -o bug.pdf \ --pdf-engine=pdflatex Error producing PDF. ! Package xcolor Error: Undefined color `DarkOrange2'. See the xcolor package documentation for explanation. Type H <return> for immediate help. ... l.56 \href{http://example.org}{link} ``` ```markdown --- urlcolor: "DarkOrange2" --- [link](http://example.org) ```

So there would need to be a change in pandoc default template so that it can works smoothly with Rmardown.

Currently, I see two workaround.

It seems you can define this is as a document class option. This seems to work

---
output:
   pdf_document:
     keep_tex: true
classoption: x11names
---
 
The next text will have a color change **\textcolor[rgb]{0,.7,.3}{LIKE THIS}**, 
or like **\textcolor{Azure1}{THIS}** 
and finally as **\textcolor{red}{THIS ONE}** ...something else.\newline

Or you can take advantage of the fact that pandoc template includes x11names for xcolor, if colorlinks is activated: Pandoc - Pandoc User’s Guide
That means you can define the color to use in the preamble, and use it

---
output:
   pdf_document:
     keep_tex: true
colorlinks: true
header-includes:
  - \definecolors{Azure1}
---
 
The next text will have a color change **\textcolor[rgb]{0,.7,.3}{LIKE THIS}**, 
or like **\textcolor{Azure1}{THIS}** 
and finally as **\textcolor{red}{THIS ONE}** ...something else.\newline

You can give a in pandoc issues so that they solve this maybe...

Cisoto · September 22, 2020, 1:26pm

IN THE NAME OF ALL GODS, THE PRESENTS AND THE ANCIENT ONES!!!!
THIS IS THE SOLUTION!!!

You will never ever can imagine how much work have you saved.

This issue is all round the web... and such a solution is the simplest one. I have learned a lot during the last 4 days... but nothing worked. This is the fast way.

There are programmers, who work on programming. But there are some people like me, that use the programming as a tool, not as our job. Some of us need this approach.

Thank you so much.

cderv · September 22, 2020, 1:42pm

I found that on the web, and it will create in your tex file this line

\documentclass[x11names]{article}

I don't really know enough Latex to understand why it works, but I imagine this works as global option for the packages loaded after. Mind the potential conflict!

I am glad it work for you now!

system · September 29, 2020, 1:42pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.