-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
A markdown_in_tex_blocks extension #2453
Comments
+1 \begin(minipage}[b]{8mm} |
Workaround for this issue was proposed here You can also add it in YAML header, on top of markdown file:
and use So @andreatta tables would look like this:
|
@jakkubu Sounds like an interesting idea. Thanks! |
this can close rstudio/bookdown#117, although a little more documentation should be provided
Why not officialize the Begin/End workaround by including it as a default header for tex and documenting it as a "parsed environment"? |
That would be great, but it is not important to me now. I have added |
@memeplex I definitely agree with you. It is just that I could wait any longer. My implementation details are totally hidden from users, so if some day what you envisioned becomes true, I can easily switch to the official approach without changing my top-level API. |
I read your https://bookdown.org/yihui/bookdown/markdown-extensions-by-bookdown.html and sees some amsthm def. Have you tried my pandoc-amsthm mentioned in #1608? And just to cross-reference what I mentioned in #3368:
|
Some comments on the hacks mentioned in this thread: The way to circumvent the pandoc's parsing of LaTeX environment is very "MultiMarkdown"-like. What I mean is it is very similar to the idea of MultiMarkdown's toggling of raw LaTeX commands. In the past (when I was from MultiMarkdown and not using pandoc yet), I have some success writing documents this way to target dual output (LaTeX and HTML). But ultimately I abandoned that approach because the source looks very ugly and hacky and difficult to maintain. (For example, a lot of text expansion might be needed to deal with the ugly syntaxes and glues and hacks.) The forte of pandoc not only lies in multiple input and output formats, but also about the filter system (allowed by the internal AST design). It takes some learning curve at the beginning, but ultimately really worth it. If some are new to filters, I suggest |
The slides now fit better to the screen irregardless of how large they originally are. The issue that you cannot format text using markdown in a Tex environment has been solved using a workaround documented here: jgm/pandoc#2453 (comment)
The extension raw_attribute solves this. (ignore the > ```{=latex}
> \begin{center}
> ```
> Remember to check **Appendix A** for additional resources references and detailed explanations.
> ```{=latex}
> \end{center}
> ``` becomes \begin{note}
Remember to check \textbf{Appendix A} for additional resources references and detailed explanations.
\end{note} |
Yes, I think using raw attributes is the solution here. |
This is a feature request to add a Markdown extension
markdown_in_tex_blocks
likemarkdown_in_html_blocks
according to the discussion in the mailing list: https://groups.google.com/forum/#!msg/pandoc-discuss/ggcrRN-ja-s/lNeILZdlBwAJ Thanks!The text was updated successfully, but these errors were encountered: