Re: How to make my latex environment accessible from markdown via short-code?

[Stefan Schroeder <ondekoza-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>]

[-- Attachment #1.1: Type: text/plain, Size: 3533 bytes --]

Denis' suggestion works as advertised. Thanks. You made my day. ☘

On Thursday, June 2, 2022 at 10:33:42 AM UTC+2 Bastien Dumont wrote:

> To complement Denis' answer, your Markdown chunks in "hint.lua" are 
> handled like strings because you created them as Str objects. What you want 
> is to return a CodeBlock (
> https://pandoc.org/lua-filters.html#pandoc.codeblock), 
> e.g. `pandoc.CodeBlock("latex", "\\begin{guidehint}")`.
>
> More generally, Pandoc has already parsed the input file when it applies 
> filters. Filters manipulate objects in the internal representation of the 
> document and should return such objects. In exceptional cases where you 
> really need to parse a Markdown string inside a filter, use pandoc.read.
>
> Le Thursday 02 June 2022 à 01:17:44AM, Stefan Schroeder a écrit :
> > I am converting markdown to pdf via latex using my own template.
> > In the template I have defined a new environment called 'hint' that is 
> like a
> > call-out.
> > 
> > This works:
> > ---
> > ```{=latex}
> > \begin{hint}
> > ```
> > Lorem ipsum dolor sit amet,
> > ```{=latex}
> > \end{hint}
> > ```
> > ---
> > The Lorem text appears in the callout-environment.
> > 
> > I want to make the environment accessible more conveniently via a 
> short-code.
> > 
> > I have created a new lua-filter, 'hint.lua' that I successfully include:
> > return {
> > {
> > Str = function (elem)
> > if elem.text == "{{hint_end}}" then
> > return pandoc.Str("```{=latex}\n\\end{guidehint}\n```\n")
> > elseif elem.text == "{{hint_begin}}" then
> > return pandoc.Str "```{=latex}\\begin{guidehint}```"
> > else
> > return elem
> > end
> > end,
> > }
> > }
> > 
> > But when I use it, the macro-text will be included literally:
> > 
> > {{hint_begin}}
> > Neque porro quisquam est,
> > {{hint_end}}
> > 
> > The code is not interpreted to end up being proper Latex, but it's 
> escaped
> > somehow to become a string literal.
> > Thus my output looks like this:
> > 
> > “‘{=latex}\begin{hint}“‘ Neque porro quisquam est, qui dolorem ipsum, 
> quia
> > dolor sit, amet, consectetur,
> > adipisci velit “‘{=latex} \end{hint} “‘
> > 
> > How do I make the short-code to get access to my own environments?
> > 
> > PS. If there are different apporaches, that'll be nice as well.
> > 
> > Thanks
> > Stefan
> > 
> > 
> > --
> > You received this message because you are subscribed to the Google Groups
> > "pandoc-discuss" group.
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email
> > to [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [2]
> https://groups.google.com/d/msgid/
> > pandoc-discuss/4de0a599-a196-438a-928c-b0895b35afb6n%40googlegroups.com.
> > 
> > References:
> > 
> > [1] mailto:pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [2] 
> https://groups.google.com/d/msgid/pandoc-discuss/4de0a599-a196-438a-928c-b0895b35afb6n%40googlegroups.com?utm_medium=email&utm_source=footer
>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/2b75bae1-51bc-49fb-84d0-d52139d9a1e3n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 5817 bytes --]