Custom-style on odt export seems not to work

[sylvaticus]

I need custom-styles in odt output but they seems not to work (they work in docx output).

MD source document:

### header

bla

this is a <span custom-style="Anote">custom style span</span>

::: {custom-style="Poetry"}
| A Bird came down the Walk---
| He did not know I saw---
:::

::: {custom-style="bluestyle"} 
I'm blue
:::

# My Header {style="Header 7"}
scscscs

this is a <span custom-style="mystyle">custom style span</span>

Pandoc Command:
pandoc test_input.md -o test_output.odt

Versions:
pandoc 2.9.2.1 --> updated to 3.5.1, didn't change anytthing
ubuntu 22.04

[iandol]

This definitely was working recently (my testing before showed divs worked but spans didn't, @jgm fixed it April 15th), see these posts:

#9656
#9657

At least out to opendocument (the text version of ODT), shows both inline and div styles working for me:

ε ➪ pandoc -v
pandoc 3.5
Features: +server +lua
Scripting engine: Lua 5.4
User data directory: /Users/ian/.local/share/pandoc
Copyright (C) 2006-2024 John MacFarlane. Web: https://pandoc.org
This is free software; see the source for copying conditions. There is no
warranty, not even for merchantability or fitness for a particular purpose.
                                                                                                                                 
Seneca in ~ 
ε ➪ pandoc -t opendocument 

[Get out]{custom-style="Strikeout"} he said.

::: {custom-style="Comment"}
This is [text with a character style]{custom-style="Teletype"}. And this is also [text with a character style]{custom-style="Highlighted"} text style.
:::

<text:p text:style-name="Text_20_body"><text:span text:style-name="Strikeout">Get
out</text:span> he said.</text:p>
<text:p text:style-name="Comment">This is
<text:span text:style-name="Teletype">text with a character
style</text:span>. And this is also
<text:span text:style-name="Highlighted">text with a character
style</text:span> text style.</text:p>

To ODT and it also works:

Note: you need to ensure the ODT template has the styles you specify, so for your styles they must be passed in using a custom ODT template. My example uses styles already present in the standard ODT template...

[iandol]

You seem all set up. FYI I also made an admonitions filter a while back that supports GFM style alerts as well as styled blocks and custom titles:

https://github.com/iandol/dotpandoc/blob/master/filters/alerts.lua

Takes markdown like:

> [!tip]
> GFM Alert.
> Some **Tip content**.
> More content: H~2~O.

> [!warning] A Custom title
> GFM Alert with custom title.
>
> My **warning** content.
> Some *more* content.

:::note
Fenced Div. 

Some note content. 
More *content*.
:::

::: {.important title="Custom Title"}
Some content.
:::

Give this ODT output:

My custom reference-doc with the styles used:

https://github.com/iandol/dotpandoc/blob/master/templates/custom.odt

[sylvaticus]

Ahhh.. I wasn't able to find your filter with Google.. well, I have learn a lot in the meantime.

One last thing.. my source is formatted to work with Markdown Preview Enhanced on VS code and uses admonitions formatted as

!!! tip mytitle
    Admonition tip using true admonition

    Still part of the admonition

Could your filter support this format ? Or it is very odd (seems to) and is pointless? It's not a big problem, I can change it on my sources...

[sylvaticus]

Using paragraph styles for the admonitions (both in your and my filter) is problematic when the admonition contain complex content, e.g. text and list items, and it would be better to wrap it in a frame with a frame-based odt style.

ChatGPT suggest to use something like this, but it doesn't work... @iandol : do you have idea how I could fix it in order to wrap the admonition in a odt frame ?

local admonitions = {
  warning   = {pandoc.Image("Warning", "imgs/admonitions/adm_warning.png"),pandoc.Space(), pandoc.Str("Warning !")},
  note      = {pandoc.Image("Note", "imgs/admonitions/adm_note.png"),pandoc.Space(), pandoc.Str("Note")},
  tip       = {pandoc.Image("Tip", "imgs/admonitions/adm_tip.png"),pandoc.Space(), pandoc.Str("Tip")},
  important = {pandoc.Image("Important", "imgs/admonitions/adm_important.png"),pandoc.Space(), pandoc.Str("Important !")},
  caution   = {pandoc.Image("Caution", "imgs/admonitions/adm_caution.png"),pandoc.Space(), pandoc.Str("Caution")},
  }
  
 local admonition_styles = {
  warning   = "Awarning",
  note      = "Anote",
  tip       = "Atip",
  important = "Aimportant",
  caution   = "Acaution",
  }


function Div(el)
  local admonition_text = admonitions[el.classes[1]]
  local admonition_style = admonition_styles[el.classes[1]]
  -- Create a new ODT frame element
  local frame = pandoc.RawBlock('opendocument', [[
    <draw:frame text:anchor-type="as-char" draw:style-name="MyFrameStyle">
      <draw:text-box>
  ]])
  
  -- Add closing tags for the frame and text-box
  local frame_end = pandoc.RawBlock('opendocument', [[
      </draw:text-box>
    </draw:frame>
  ]])
  
  if admonition_text then
    table.insert(el.content, 1,
        pandoc.Para{ pandoc.Strong(admonition_text)})
  end  

  -- Add the original content inside the frame
  return {
    frame,
    pandoc.Div (el.content, {["custom-style"] = admonition_style}),  -- Original content inside the frame
    frame_end
  }
end

[sylvaticus]

Well, the matter was simply to wrap the <draw:frame> in a <text:p> node :-)

[iandol]

Could your filter support this format ?

Probably, but it is a strange format that conflicts with the use of indentation for code blocks. It would be more convoluted than the GFM mode (which itself abuses quotes) or simple plain divs. Personally I would stick to divs. Wrapping in frames for ODT is a good idea!