-
-
Notifications
You must be signed in to change notification settings - Fork 872
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
double quotes in restructuredText figure captions erroneously being converted to html #2023
Comments
And issue is from here: Line 59 in 3237add
We should escape really only when the output format supports it. |
However, this happens because the caption for rst output uses Lines 5 to 19 in 3237add
I don't know a lot about asciidoc yet. Is there a way to add alt text for figures ? |
I've never used |
Sorry I just for mixed up. rst is for I see how I can make rst support the new |
Correct. In a rst "figure" directive you can specify a separate
|
…alt text can be independently specified via the fig.alt option (#2269) Co-authored-by: Yihui Xie <xie@yihui.name>
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary. |
I've recently noticed in my knitted README and blog posts that double quoted figure captions in restructuredText documents are now being erroneously converted to html in recent versions of
{knitr}
.{knitr}
didn't used to do that so this seems to be new{knitr}
bug introduced sometime "recently".Contents of minimal example
test.Rrst
:when knit by
knitr::knit("test.Rrst")
becomes:Instead of
"double"
we should instead see"double"
in both places it appears in the knit.rst
document.Thanks!
By filing an issue to this repo, I promise that
xfun::session_info('knitr')
. I have upgraded all my packages to their latest versions (e.g., R, RStudio, and R packages), and also tried the development version:remotes::install_github('yihui/knitr')
.I understand that my issue may be closed if I don't fulfill my promises.
The text was updated successfully, but these errors were encountered: