Skip to content
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

Closed
krlmlr opened this issue Nov 2, 2017 · 4 comments
Closed

LaTeX compatibility #27

krlmlr opened this issue Nov 2, 2017 · 4 comments

Comments

@krlmlr
Copy link
Member

krlmlr commented Nov 2, 2017

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):

knitr:::is_latex_output(). This function was exported recently in the devel version of knitr.

Should we work along these lines? Or should knitr (or even the user) just set the cli.unicode option?

@gaborcsardi
Copy link
Member

gaborcsardi commented Nov 2, 2017

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 cli.unicode to FALSE. I am not sure whose responsibility this is.

@krlmlr
Copy link
Member Author

krlmlr commented Nov 2, 2017

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.

@gaborcsardi
Copy link
Member

@krlmlr so we should do this in cli as well?

@krlmlr
Copy link
Member Author

krlmlr commented Nov 2, 2017

That's what I'd suggest. Eventually pillar will use cli.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants