I know there is a way to color fonts by using HTML tag in this way: <span style='color:green'>TEST</span>
But when I do something like <span style='color:green'>## TEST</span>, the headers feature will not appear, i.e. the font size is not enlarged.
Is there a neat way to color headers in markdown in Jupyter Notebook without using lengthy css stuff? Thanks.
I have tried searched a lot on Google and Stackoverflow but I still cannot find a solution to my problem. I am expecting a solution. Thanks.
On github and gitlab you can use KATEX who can help with good codes like \color{colorname} who change the color from the text inside the $$$$ code, like below:
# $${\color{purple} \boxed{ \frak{ \color{orange}Rise \space \color{cyan}and \space \color{magenta}Rise \space \color{lime}again \space \color{violet}until \space \color{lightgray}Lambs \space \color{teal}become \space \color{red}Lions !} } }$$
On github profile:
Like jupiter use almost the same markdown, you can check if you can use LATEX or KATEX code.
More info about LATEX on jupyter here: towards data science - markdown latex on jupyter
I am using bookdown to write some maths lecture notes. I find myself very often using the > blockquote feature. Often, this is because my environments, such as remarks and exercises take multiple lines. It is then ambiguous where the theorem ends and where 'chat' begins after.1 I'm pretty happy with doing this. I like the fact that the blockquote singles out the environments so it's very easy to see when one is changing to another. The thing I don't like is that it "softens" the text colour.
See the following screenshot, comparing the boldness of the font in the first paragraph with that in the blockquote.
Is there any way of removing this "softening"?
1
LaTeX gets around this by adding extra white-space around something like \begin{example} ... \end{example}. Alternatively, one can configure them to add a \qedsymbol to indicate that they have come to an end. I don't feel the first option would look nice in bookdown and I don't think the second option is even possible. It would actually be great for my long examples if it did!
Per your request, you can change the styles in HTML outputted R Markdown scripts by adding styles. There are a few different ways you can add them. Typically, I just place this content in between chunks.
<style>
blockquote {
font-color: black;
opacity: 1;}
</style>
You can attach an external style document or use a CSS chunk. I just find this easier for most projects.
You can read more about this here.
I know I can set fig.align = 'center' if I want to center my figure. But what if I want to center my output in a pdf document?
The following code worked for me.
\center Centered Text \center
And, if you need to put it in bold, as my case, you can use the underline (two at the beggining, two at the end):
\center __Centered Text__ \center
Hopefully it is not too late to add my answer.
You can use html tags in Rstudio Markdown documents.
To center a text you just need to:
<center> TEXT TO CENTER </center>
This works for me when knitting Rstudio Markdowns.
The option for centering a plot you generated by R code in Rmd file and that for an existing figure from a file elsewhere is different.
For the figures you generated in R, I think fig.align="center" is sufficient, even if you want a PDF output.
For <center> <\center> to work, you can only use an HTML output. If you still want PDF output, I think you can use include_graphics(your_img.png) from knitr package, and then you can use chunk options like fig.align="center". If you also want to change the size of this figure, please use something like out.width="50%", but not fig.width.
For more details, I found this article really useful tips and tricks for working with images and figures in r markdown documents.
So I've been using R markdown to make some reports and I decided to spruce it up a bit by using the Foundation 4 CSS framework with it.
I embedded the minimized Foundation css in the file and then applied the styles to the R markdown code and it works fine but the quality of the image that is coming out is much lower than what was coming out via just R markdown.
Inside the R code I have:
cat('<div class = "Row">')
cat('<div class = "Foundationy grid columns">')
Bunch of R plot code here
cat('</div>')
etc...
I guess Foundation is changing the image quality somehow?
Any ideas on what I can change in the CSS to fix this?
I switched to Toast which is a much more lightweight CSS framework and the problem disappeared.
I'm assuming Foundation has some style that effects images. I didn't locate the style but switching frameworks was a decent workaround.
I previously asked a question about how to export a HTML table in R and have control over line borders.
I'm used to LaTeX where when you create a table, the formatting of the table is largely determined by the text and markup that appears at that point. This works well for Sweave, because your R code chunk can output LaTeX table markup at that point. I also understand that there are tools like xtable that can produce HTML markup for a table.
However, control over HTML tables seems to rely on style sheets, which are meant to appear in the header of the document and not in the location where the R code chunk is placed. Of course, I could just put content in the style sheet, but in scientific applications often there can be some quite specific table formatting that varies in some respects from table to table.
Thus, my question:
In general, how do you format an HTML table with literate programming like R Markdown or even from raw HTML if formatting of the output requires output to be created in a separate place in the document (i.e., CSS for the table in the header) to where the R code chunk is placed (i.e.,the table itself in the body)?
I can think of three ways without messing with your toolchain, all of them are kind of hacky.
Just output the <style> right in the body. This isn't technically valid, but it will work fine in any major browser.
Emit JavaScript that creates a <style> block at runtime and appends it to the head (here's one way). This will look a little gross in the HTML source and in the R code, but it will work and it will validate.
Use a scoped style block. This would be exactly what you are looking for, except that the scope attribute is new to HTML5 and not yet implemented in any major browser. However, if you base your styles on uniquely generated IDs (i.e. your rules are written such that even if they apply to the whole document they won't mess anything up), I imagine the browsers will just ignore the "scoped" attribute and everything will work properly--then this becomes effectively a version of option 1 that happens to validate!
(I would go with #3, personally.)
If you haven't already, it'd be worth starting a thread at the RStudio support forum about this; even though it's not strictly an RStudio issue, we're obviously doing a lot of work on the end-to-end scenario of publishing reports in R Markdown and would love to find out more about your specific examples. Tables are clearly going to be a big part of what people do with this reports and we know this is a weak spot right now, one that we do want to address in future versions.
An alternative method would be to use pander as R markdown backend (sorry for this marketing-like answer, but I do think my Pandoc.brew function could be really handy for this purpose).
It is similar to knitr (parsing/evaling R commands in a markdown formatted file) but using brew syntax for R code blocks (e.g. <%...%> for general R code - like loops etc. and <%=...%> for returning results in a block). But differs from brew as Pandoc.brew does not only cat results in a code block, but runs my pander generic method which transforms (quite q wide variety of) R objects to (IMHO) pretty Pandoc's markdown format.
So running Pandoc.brew on a markdown formatted file would result in a clean markdown file with all R code blocks run - and you do not have to deal with xtable and other tweaks (not even with plots as all R code blocks resulting in an image is rendered to a png file and linked in the markdown text file).
And about why I started to answer here: with pander you can pass special options to pandoc, e.g. adding a custom CSS stylesheet (or JS etc.) to your generated HTML's header, see details on Pandoc's homepage. Based on that you could easily add your CSS file(s) or even just a bunch of style parameter. This could be done in pander with Pandoc.convert's option. BTW you do not even have to use my forked brew function, you can generate your markdown file with e.g. knitr and call Pandoc with the above function.
pander adds some CSS/JS to generated HTML files, which would generate (IMHO) quite pretty output, but you can easily customize that and adding your own files there.
For example: you would get this HTML file based this markdown by default which was Pandoc.brewed from this quite short markdown syntax brew file. BTW my github page was also generated/automatically styled by my markdown parser. I would really appreciate if you would try it :)
NOTE: to try the above calls you would need Pandoc pre-installed, also you'd need an up-to-date version of both rapport, both pander. See installation details.
One option which doesn't completely solve the problem is to use gvisTable:
Here is a basic gvisTable:
```{r message=FALSE}
# install.packages("googleVis")
library(googleVis)
library(MASS)
data(Animals)
```
```{r results='asis'}
tab1 <- gvisTable(Animals,
options = list(width = 600, height = 650,
page = "enable",
pageSize = nrow(Animals)))
print(tab1, "chart")
```
?print.gvis explains some of the options for printing the gvis object.
In partiuclar the tag="chart" option is required for R Markdown documents as this means that the output is just what is required for the object, rather than a complete HTML page as is the default.
See the output of this and a little more here
Ok, hope I got it now. You should set some additional knitr options, and you could cat() the css dynamically if you like.
<!DOCTYPE html>
<head>
<style type="text/css">
.greenback {
background-color: teal;
color: white;
}
.greenback td {
border: dotted gray;
}
.bluescreen {
background-color: blue;
color: white;
}
.bluescreen td {
border: thick solid;
padding:2px;
margin:2px;
}
</style>
</head>
<body>
<table class="greenback">
<tr><td>Hello</td><td>Mars</td><tr>
<tr><td>World</td><td>Moon</td><tr>
</table>
Could use some xtable code here instead.
<!--begin.rcode
cat('
<table class="bluescreen">
<tr><td>Hello</td><td>Mars</td><tr>
<tr><td>World</td><td>Moon</td><tr>
</table>
')
end.rcode-->
</body>
</html>
Neil Saunders has a tutorial on customising CSS for HTML generated using RStudio. It shows how you can modify the built in style file and source this alternative file.