-
Notifications
You must be signed in to change notification settings - Fork 19
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
NA
processing with Quarto doesn't work
#263
Comments
Thanks a lot for the report @cbgoodman . The primary issue should be fixed on Github now. Unfortunately, investigating this brought to my attention two more issues in dealing with Quarto. Issue 1: Special charactersWhen compiling to LaTeX, Quarto will sometimes interpret some Base64 encoded strings as Markdown code. For example, if you call I recommend you use a "non-markdown" character or an empty space when replacing See below for an example. Issue 2: Quarto data processing in LaTeXI believe that This works in HTML but unfortunately not in LaTeX. @andrewheiss once linked to this thread when explaining that the strategy only worked for HTML. Andrew, do you know if a new workaround was proposed? I see that the original Quarto issue has been closed, but I can't quite figure out what the recommeded strategy is. Example
|
Thanks, @vincentarelbundock! I wish my bug reports had not uncovered fundamental issues with Quarto processing, but this isn't the first time it's happened. 🤷♂️ |
Oh, right, context. I've been pestering @andrewheiss with Quarto bugs that are really not implemented features (that are also poorly documented) for ages. |
Can confirm the special characters issue is solved. The secondary issue still remains, but I expected that. |
Thanks for confirming. Closing because there is probably nothing I can do to fix the rest here. |
When asking
tinytable
to process NA's withquarto = TRUE
, there's no processing with TeX.Works fine with HTML (and Quarto processing turned off)
The text was updated successfully, but these errors were encountered: