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

Bibliography file name #22

Closed
antaldaniel opened this issue Nov 23, 2017 · 2 comments
Closed

Bibliography file name #22

antaldaniel opened this issue Nov 23, 2017 · 2 comments

Comments

@antaldaniel
Copy link

This is not strictly a bookdown issue, but if you use bookdown on Windows, you will encounter similar problems and I believe for an average user like me it takes very long time to figure out some of them, because the error messages are very confusing in the workflow.

I think this merits maybe a warning in the code, or at least a words in the documentation.

This is BibTeX, Version 0.99d (MiKTeX 2.9.6500 64-bit)
The top-level auxiliary file: bookdown-demo.aux
The style file: apalike.bst
White space in argument---line 35 of file bookdown-demo.aux
 : \bibdata{book,packages,music\protect
 :                                      \TU\textunderscore report3}

I had a .bib filename music_report3.bib, and it gets some whitespace characters that create errors. Similarly, if you have chunks that have hyphens, such as music-report can create problems.

I am not experienced at all in LaTex, bookdown, which is probably my favorite package, brought me into using it, so figuring out these problems took me always a very-very-very long time. Maybe it would be a idea to add a table somewhere in the bookdown book, or some warnings that contain a table about avoidable variable / chunk / file / component naming that may cause a program in the interaction of bookdown / rmarkdown / knitr / external latex programs.

@yihui
Copy link
Member

yihui commented Nov 23, 2017

Duplicate of rstudio/bookdown#491

@yihui yihui marked this as a duplicate of rstudio/bookdown#491 Nov 23, 2017
@yihui yihui closed this as completed Nov 23, 2017
@antaldaniel
Copy link
Author

Sorry about the duplication.

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