One way to think about it: it's not about input / output but about format. HTML has &lt;div&gt; and &lt;span&gt; in its definition, that's not optional; Pandoc's internal representation (AST) has Div and Span elements, that's not optional. But whether markdown includes Div / Span syntax ('native_divs' and 'native_spans') is optional, hence the option is on the markdown format, not on the html format. <br /><div><br /></div><div>For example if you were writing *to* markdown you could remove Div and Spans with pandoc  -t markdown-native_divs-native_spans</div><div><br /></div><div>J<br /></div><div><br /></div><div class="gmail_quote"><div dir="auto" class="gmail_attr">On Thursday, February 23, 2023 at 7:05:36 AM UTC Brian Granger wrote:<br/></div><blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div>Looks like asking the question was enough for me to see it in a new light. My mistake was applying the extension to the output format rather than the input format. Thus, the following works:</div><div><br></div><div><span><span>pandoc -f html-native_divs-native_spans -t markdown</span></span></div><div><span><span><br></span></span></div><div><span><span>But this doesn&#39;t:</span></span></div><div><span><span><br></span></span></div><div><span><span><span><span>pandoc -f html -t markdown<span><span>-native_divs-native_spans</span></span></span></span></span></span></div><div><span><span><span><span><span><span><br></span></span></span></span></span></span></div><div><span><span><span><span><span><span>I don&#39;t understand how to think about when to apply extension to the input versus the output format, but I do have a solution that enables me to move forward.</span></span></span></span></span></span></div><div><span><span><span><span><span><span><br></span></span></span></span></span></span></div><div><span><span><span><span><span><span>Cheers,</span></span></span></span></span></span></div><div><span><span><span><span><span><span><br></span></span></span></span></span></span></div><div><span><span><span><span><span><span>Brian<br></span></span></span></span></span></span></div><div><span><span><br></span></span></div><div><span><span><br></span></span></div><br><div class="gmail_quote"><div dir="auto" class="gmail_attr">On Wednesday, February 22, 2023 at 10:53:22 PM UTC-8 Brian Granger wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Hi all,</div><div><br></div><div>I am working on a usage case where I want to generate simplified, clean Markdown without any explicit HTML tags or extended syntax such as the fenced divs syntax (<span><span>:::::)</span></span>. I only need to preserve the basic content of the HMTL such as section headers, paragraphs, links, code blocks, etc. and don&#39;t need (or want) any of extra content that would be put into HTML tags. I have played with different Markdown format in Pandoc, filters, and existing extensions, but haven&#39;t been able to achieve this yet. Does anyone have any ideas or tips of things to try?<br></div><div><br></div><div>Thank you!</div><div><br></div><div>Cheers,</div><div><br></div><div>Brian<br></div></blockquote></div></blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &quot;pandoc-discuss&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org">pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org</a>.<br />
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/pandoc-discuss/7bc05dcb-7a1a-49fd-9467-dbec7a135720n%40googlegroups.com?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/pandoc-discuss/7bc05dcb-7a1a-49fd-9467-dbec7a135720n%40googlegroups.com</a>.<br />