Replies: 8 comments 36 replies
-
|
@tbeason can you provide a example of somewhat problematic table that you have? |
Beta Was this translation helpful? Give feedback.
-
|
The main thing that is missing for me in Markdown is variable row spacing. For example, if I am outputting regression estimates and standard errors as "grouped rows", typically I would end a standard error line in latex like this: |
Beta Was this translation helpful? Give feedback.
-
|
Alternatively, if there was a way to not double space a particular table when it is converted from Markdown, that could also solve my particular problems right now. My document uses |
Beta Was this translation helpful? Give feedback.
-
|
@tbeason Consider the following example inspired by the esttab documentation: When you render your Quarto document to PDF with LaTeX,
That is the output that you want. |
Beta Was this translation helpful? Give feedback.
-
|
I do not think this really solves my problem. I know how to make and output the table in latex. I guess I offered up more gripe than I should have since you asked about the table. I don't think there is a good way to make the table using Markdown syntax, but that isn't such a concern because I am fluent (enough) in latex. The real problem is that, in my document, I want to be able to refer to a latex table the same way that I can refer to a Markdown table: using the |
Beta Was this translation helpful? Give feedback.
-
|
I tried this out and had the same result. Nothing when I include a LaTeX table in a qmd (or Rmd) file. I even tried This makes no sense. Pandoc coverts simple LaTeX tables just fine to HTML. It is often used as a LaTeX to HTML coverter. @cscheid Any idea what's wrong? I don't think it's a Quarto specific issue as I saw it in R Markdown too. Pandoc knows how to convert LaTeX tables to HTML, but for some reason is not 'doing its magic' on them here. Usually it is pretty smart about dealing with LaTeX embedded in markdown. |
Beta Was this translation helpful? Give feedback.
-
|
@eeholmes The way that Quarto works is
Consider the minimal working example that you provided before: The output of The output of When you use |
Beta Was this translation helpful? Give feedback.
-
|
Whew, we're deep into Pandoc weeds here, so let's first make sure we are all in the same page. Raw Block Syntax
Here's the internal Pandoc representation of a couple of different documents: Compare that to this: This internal representation takes a bit of work to read at first, but you can tell that if we use instead of What @rgaiacs meant originally about this syntax being designed for "please send this block directly to the latex format and only the latex format" is true, but it holds for the code-block syntax, not the div syntax. Format Portability for TablesLet's go back to the point of this discussion: how to get tables in multiple formats. What @eeholmes was referring to is (probably, pls correct me if I'm wrong!) this: So pandoc can convert from LaTeX to markdown and html tables (!!). This is what's truly powerful about Pandoc, if you've never seen it before. It not only generates many output formats, it reads many input formats as well. However, it requires us telling pandoc that the input format is LaTeX, which is not the case in quarto. If you try the following, it will not work: This will not generate the content, for the same reason that "But none of this solves my problem!"Sadly, no. Ultimately, I think that what @tbeason wants to do is currently not easy in Quarto. We have plans to improve our crossref infrastructure for 1.2. It's possible that we will end up in a place where we can add "raw references", but we won't commit to it because it's quite a complicated feature with a lot of moving parts. |
Beta Was this translation helpful? Give feedback.
-
|
Followup, there's a related trick we already do in quarto, which is that if you use HTML tables as input, we will convert them to LaTeX for you. Currently, we only do this for HTML table inputs, but we might change that in the future. |
Beta Was this translation helpful? Give feedback.
-
|
@cscheid Thanks for the deep dive into Pandoc! Yes, you captured what I was getting at. The effect I showed was the same whether or not My idea with using For example, I use |
Beta Was this translation helpful? Give feedback.
-
That's right. The issue is that Pandoc needs to know that the input is latex to convert correctly. And, in quarto, our input is always Markdown.
Yes, but what you're telling Pandoc is that whatever is inside this block, it should appear only when the output is LaTeX. I think you're thinking of it as "Pandoc: here's some LaTeX input, do the right thing with it now". And, to be clear, when you use the
I'm not 100% sure. But I think it's simply because Pandoc treats |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, it seems to me that Both of these render fine to html and the But yes, I would like Note the reason I find this interesting is that if a block like |
Beta Was this translation helpful? Give feedback.
-
I want to come back to How are you getting these
Unfortunately, we don't control that syntax; Pandoc does.
Can you tell me about some of these new things? We've been thinking about a similar feature but we could only think of tables as a valid use case for it. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, maybe ```{=latex}
...
```
makes more sense for this application. Even if currently it means "ignore unless latex", that doesn't have to be the interpretation. Regarding other applications. Well Pandoc can translate to-from all kinds of things: https://pandoc.org/
```{=docx}
{{< include theword.docx >}}
```
We hack processes like this now and this would be better. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the added context. Compared to the table use case, I expect these to be quite a bit less common, and they offer a number of additional complications that I think we'd prefer not to support. (For example, if we're including theword.docx directly, we need to now worry about figure insertion, cross-reference resolution, etc.) With that said, if you're willing to go the lua filter route, all of these are possible to implement by yourself: see https://pandoc.org/lua-filters.html#pandoc.read. |
Beta Was this translation helpful? Give feedback.
-
|
I believe that I understand what @tbeason and @eeholmes want and why this is "hard" to implement. They want to have Quarto/knitr/Jupyter generating the and Pandoc create the internal structure instead of In other words, they want Pandoc to also convert the LaTeX or TeX raw blocks created when reading the input as Markdown to The best solution is the lua filter route suggested by @cscheid. Why does Pandoc process LaTeX equation but not LateX tables in Markdown?Render math in the web has being challenge since the creation of the web. W3C addopted MathML but all browsers didn't implemented it. The solution that people used for years was to have authors writing the equations in LaTeX and the server processing the LaTeX equations and create images. Recently, MathJax allowed LaTeX equations to be processed in the reader's web browser. Because of this, Pandoc's implements "special" support for LaTeX math part. For example, consider the following The output of Pandoc will keep all LaTeX math elements. Now compare it to the output of Note that Pandoc removed the display ( Pandoc will use raw TeX block for the display math element. Today, most projects use MathJax, including Quarto, and the call to Pandoc is With |
Beta Was this translation helpful? Give feedback.
-
|
We had a similar issue in a JOSS submission. Our solution was to parse all raw LaTeX blocks and inlines into pandoc's internal document format, except when we converting to/via LaTeX. I've published the filter as a quarto extension: tarleb/parse-latex. If I understand the discussion correctly, then this could be sufficient to resolve the issue: quarto install extension tarleb/parse-latexThen in the filters:
- parse-latex |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, I'd be nice if something like the below worked for html and latex. Maybe the filter can be modified to get this to work. To my mind the ```{=latex}
syntax makes more sense as it is not just a div with class, but it is a code block. I am saying, "this is a type of code block and I want to use the commands (chunk yaml |
Beta Was this translation helpful? Give feedback.
-
|
@eeholmes Under that syntax, that's not behavior we can control, because it's actually Pandoc syntax. We choose not to override Pandoc syntax since that would be extremely confusing for Pandoc users. |
Beta Was this translation helpful? Give feedback.
-
|
@eeholmes I will note that in the specific case of html tables, quarto does convert them to latex:
Note that this is a case in my "this is extremely confusing for Pandoc users" point! We're probably going to improve the behavior here so that it's generally applicable to any format, and uses a less-confusing syntax. |
Beta Was this translation helpful? Give feedback.
-
|
Completely unrelated comment, but it is weird to me that ```{python}
works but ```{html}
```{latex}
do not. I keep wanting to do something like ```{html}
#| div: class="abc"
because I've gotten used to |
Beta Was this translation helpful? Give feedback.
-
|
The mnemonic to keep in mind is that braces without the equals sign means computational content: stuff that needs to be executed by another program and that generates an output: so those go for things like In addition, these are the only blocks that understand hash-pipe syntax. braces with the equals sign mean "pass this as-is to the specific Pandoc format" (aside from that special case in html tables, which I still contend is very confusing behavior on the part of quarto!) |
Beta Was this translation helpful? Give feedback.
-
|
@cscheid It was the cross-reference part that is not being used. The OP's question was about cross-references. I know there are probably other ways to do this for html but not for latex. ```{=html}
#| label: tbl-one
#| tbl-cap: This is table one.
My point here was that, "oh, if this cross-ref syntax worked for html, then it should be easy to get this to work for latex by extending somehow the OP's lua filter." if I do this ```{r}
#| label: tbl-one
#| tbl-cap: This is table one.
--code that outputs html or latex--
```
Then the cross-reference works, but it doesn't work if I put the html or latex there raw. |
Beta Was this translation helpful? Give feedback.
-
|
I totally understand! I'm just trying to give as much context to the current state of quarto and our decisions as I can. With that said, here's how you'd make it all work, although it's completely atrocious: That .qmd produces this output:
|
Beta Was this translation helpful? Give feedback.
-
|
@tbeason If you truly, absolutely need it right now, look at the above code :) But if you can wait two or three months, we are working on a much better solution for v1.2. |
Beta Was this translation helpful? Give feedback.
-
|
Ugly hack but shows how it can be done. For R users, {xtable} has a LaTeX to html function. So you can read the latex into a string, use the xtable latex to html converter function and then the hack above. |
Beta Was this translation helpful? Give feedback.
-
|
Do I understand correctly, though, that the |
Beta Was this translation helpful? Give feedback.
-
|
@tbeason that exact case (i.e., cross-referencing of tables) was the original motivation for the filter. So, yes, it should work for that. (But it's still software, so I'll stay with the conjunctive mood.) |
Beta Was this translation helpful? Give feedback.
-
|
Here is a test of @tarleb 's filter. @tbeason ---
title: "test"
format:
html: default
pdf:
keep-tex: true
editor: source
filters:
- parse-latex
---
This is a reference to Table @tbl-one.
```{=latex}
\begin{table}
\caption{caption of table.}\label{tbl-one}%
\begin{center}
\begin{tabular}{ c c c }
cell1 & cell2 & cell3 \\
cell4 & cell5 & cell6 \\
cell7 & cell8 & cell9
\end{tabular}
\end{center}
\end{table}
```
PDF output: Note if I use
HTML output:
|
Beta Was this translation helpful? Give feedback.
-
|
Do you know why it added the caption as "(a) caption of table" instead of adding to "Table 1: caption of table" |
Beta Was this translation helpful? Give feedback.
-
|
I don't really understand what's going on there. It seems to be some weird interaction of Quarto and pandoc's LaTeX parser, more specifically their use of Div wrappers. |
Beta Was this translation helpful? Give feedback.
-
|
It seems that Quarto expects the ID to be encoded in the table's caption and gets confused if the table has an ID in the pandoc AST. function RawBlock (raw)
if raw.format:match 'tex' then
return pandoc.read(raw.text, 'latex').blocks:walk {
Div = function (div)
local tbl = div.content[1]
if #div.content == 1 and tbl.t == 'Table' then
local idstr = string.format('{#%s}', div.identifier)
if #tbl.caption.long == 0 then
tbl.caption.long = pandoc.Blocks{pandoc.Plain(idstr)}
else
tbl.caption.long[1].content:insert(idstr)
end
return tbl
end
end,
}
end
end |
Beta Was this translation helpful? Give feedback.
-
|
The best workaround that I found was to use LaTeX syntax like if FORMAT:match 'latex' then
return {}
end
function RawBlock (raw)
if raw.format:match 'tex' then
return pandoc.read(raw.text, 'latex').blocks:walk {
Div = function (div)
local tbl = div.content[1]
if #div.content == 1 and tbl.t == 'Table' then
local idstr = string.format('{#%s}', div.identifier)
if #tbl.caption.long == 0 then
tbl.caption.long = pandoc.Blocks{pandoc.Plain(idstr)}
else
tbl.caption.long[1].content:insert(idstr)
end
return tbl
end
end,
}
end
end
function RawInline(raw)
if raw.format:match 'tex' then
return pandoc.utils.blocks_to_inlines(
pandoc.read(raw.text, 'latex').blocks:walk {
Link = function (link)
local ref = link.attributes.reference
if ref then
return pandoc.Cite(
'@' .. ref,
{pandoc.Citation(ref, 'AuthorInText')}
)
end
end
}
)
end
endI'm not comfortable with actually using something like that, but it does the job: Both the HTML and PDF output look ok. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm yea not ideal. I am not sure what I will do. I guess temporarily I can just remember which tables I need to reference using raw latex. Could there be a different solution? For example, if Quarto cannot find the reference for |
Beta Was this translation helpful? Give feedback.
-
Markdown tables work well for simple tables. I also like the
@tbl-namecross-reference ability provided by Quarto. However, I have some tables that are somewhat problematic to write using Markdown and have them look nice. I know I can just put the raw latex in the file, but then I lose the ability to reference it using the same syntax. Is there a way to hack things together so that I can still reference latex tables using the@syntax?Beta Was this translation helpful? Give feedback.
All reactions