You are completely right!
The second part is what I was doing wrong.

Thanks for clarifying it.

The attribute is helpful as it allows to use custom styles on your docx (output).

Thanks again,
  Agustín.

On Tuesday, October 31, 2017 at 1:58:17 PM UTC+1, Philip Hodder wrote:
Hi

I've also been testing this (been after this feature for ages!), I think your confusing the class notation with the custom attribute notation. Try this

::: MyStyle 
Paragraph here
:::

which will create

<div class="MyStyle">
Paragraph here
</div>

or this

::: {custom-style="My Style"}
Paragraph here
:::

which I believe will give you

<div custom-style="My Style">
Paragraph here
</div>

although I'm not sure an attribute of that name will be helpful...

Phil

On Tuesday, October 31, 2017 at 11:37:29 AM UTC, Agustín Martín wrote:
I was trying to test the `fenced_divs` extension in pandoc 2.0.

I expected that it would behave like raw html divs, and thus I also expected

:::: {.custom-style="My Style"}
Testing custom style: "My Style"

Several lines.
::::

to behave the same as

<div custom-style="
My Style">
Testing custom style: "My Style"

Several lines.
</div>

when converting from markdown to docx.

However the first approach is not working, I even see the ":::: {...}" in the output document.

Did I misunderstand the use case for fenced_divs?

Thanks!

--
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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/69e181bc-a47c-4a02-8ec5-47046424220f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.