Filter for inline syntax extensions

Filter for inline syntax extensions

[Albert Krewinkel]

I've been playing around with a filter that adds additional markup
syntax. In my example it uses `==highlight==` to add highlighted text.
Highlighted (`mark`ed) text is only supported with HTML output, support
for other formats would need some extra work.

The filter comes with all the downsides of adding a second parsing step,
but it works well in most cases. It can also be modified to support
different markup.
<https://gist.github.com/tarleb/a0646da1834318d4f71a780edaf9f870>

-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124

Re: Filter for inline syntax extensions

[Laurent Duperval]

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

HI,

I know this message is pretty old but is there a place where I can find 
this extension and how it works?

I'm using the highlight.lua approach from here 
(https://gist.github.com/tarleb/a0646da1834318d4f71a780edaf9f870) and it 
works when exporting to PDF but not when exporting to ODT or DOCX. I'm not 
sure why. I would relly like a way to make this work reliably with ODT.

Thanks,

L

On Saturday, July 16, 2022 at 5:00:01 AM UTC-4 Albert Krewinkel wrote:

> I've been playing around with a filter that adds additional markup
> syntax. In my example it uses `==highlight==` to add highlighted text.
> Highlighted (`mark`ed) text is only supported with HTML output, support
> for other formats would need some extra work.
>
> The filter comes with all the downsides of adding a second parsing step,
> but it works well in most cases. It can also be modified to support
> different markup.
> <https://gist.github.com/tarleb/a0646da1834318d4f71a780edaf9f870>
>
> -- 
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>

-- 
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/b1e8933e-04eb-47b7-9cbb-2a5a58ea51c5n%40googlegroups.com.

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

Re: Filter for inline syntax extensions

[Albert Krewinkel]

Hi Laurent,

Laurent Duperval <lduperval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> I'm using the highlight.lua approach from here (https://
> gist.github.com/tarleb/a0646da1834318d4f71a780edaf9f870) and it works
> when exporting to PDF but not when exporting to ODT or DOCX. I'm not
> sure why. I would relly like a way to make this work reliably with
> ODT.

This depends on the pandoc writers for each format. As noted in my
original message, support for other formats requires more work.

The additional work to get support for ODT and docx is rather minimal
though: change lines 27-29 to

    local function markup_inlines (inlines)
      local attr = {class='mark', ['custom-style']='Highlighted'}
      return pandoc.Span(inlines, attr)
    end

The text can then be style via the 'Highlighted' character style.

-- 
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe  e836 388d c0b2 1f63 1124

Re: Filter for inline syntax extensions

[Laurent Duperval]

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

Hmmm...

Something isn't working.

This is my Input:

# Testing highlights

==highlight==

==highlight==

This is the text portion of the content.xml output:

<office:body>
<office:text>
<text:h text:style-name="Heading_20_1" 
text:outline-level="1"><text:bookmark-start text:name="testing-highlights" 
/>Testing highlights<text:bookmark-end text:name="testing-highlights" 
/></text:h>
<text:p text:style-name="First_20_paragraph">highlight</text:p>
<text:p text:style-name="Text_20_body">highlight</text:p>
<text:p text:style-name="Text_20_body"></text:p>
</office:text>
</office:body>

I will need to dig in to understand what's (not) happening.

When I export with PDF it works. I use Typora which seems to have its own 
PDF export engine that recognizes the highlighting. 

I have to install a complete LaTeX package to test the PDF output from a 
vanilla Pandoc export. For now, though, it looks like the LUA file isn't 
taken into consideration.

L

On Monday, November 14, 2022 at 2:50:13 AM UTC-5 Albert Krewinkel wrote:

> Hi Laurent,
>
> Laurent Duperval <ldup...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > I'm using the highlight.lua approach from here (https://
> > gist.github.com/tarleb/a0646da1834318d4f71a780edaf9f870) and it works
> > when exporting to PDF but not when exporting to ODT or DOCX. I'm not
> > sure why. I would relly like a way to make this work reliably with
> > ODT.
>
> This depends on the pandoc writers for each format. As noted in my
> original message, support for other formats requires more work.
>
> The additional work to get support for ODT and docx is rather minimal
> though: change lines 27-29 to
>
> local function markup_inlines (inlines)
> local attr = {class='mark', ['custom-style']='Highlighted'}
> return pandoc.Span(inlines, attr)
> end
>
> The text can then be style via the 'Highlighted' character style.
>
> -- 
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>

-- 
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/a6a7faa7-3c96-4661-a907-9ba357a41d04n%40googlegroups.com.

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