-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LaTeX compatibility #27
Comments
One good way would be to use a modern unicode alternative like xetex. I am not sure if this is easy with knitr or not. Yes, the other way would be to set |
The PDF has been produced with xetex; plain pdflatex will give errors. It feels easiest to query for LaTeX output here than the other way round. Example: r-lib/pillar@170deca9. |
@krlmlr so we should do this in |
That's what I'd suggest. Eventually pillar will use cli. |
Many symbols do not render properly in a LaTeX document: LaTeX.pdf. What's the best way to deal with this?
We can detect if LaTeX output is active, r-lib/pillar#61 (comment):
Should we work along these lines? Or should knitr (or even the user) just set the
cli.unicode
option?The text was updated successfully, but these errors were encountered: