to have been traversed before you add '

' and= '

'?). >> >> With the custom writer shown below, and with an input file that consists= of the single line 'Text' (and using my logging module ), you get this with the default 'typewise' traversal: >> >> (#) inline Str "Text" >> (#) inlines Inlines[1] {[1] Str "Text"} >> (#) block Para {content: Inlines[1] {[1] Str "Text"}} >> (#) blocks Blocks[1] {[1] Para {content: Inlines[1] {[1] Str "Text"}}} >> (#) meta Meta {} >> (#) doc Pandoc { >> =C2=A0 blocks: Blocks[1] { >> =C2=A0 =C2=A0 [1] Para { >> =C2=A0 =C2=A0 =C2=A0 content: Inlines[1] { >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 [1] Str "Text" >> =C2=A0 =C2=A0 =C2=A0 } >> =C2=A0 =C2=A0 } >> =C2=A0 } >> =C2=A0 meta: Meta {} >> } >> >> ...and this with 'topdown' traversal: >> >> (#) doc Pandoc { >> =C2=A0 blocks: Blocks[1] { >> =C2=A0 =C2=A0 [1] Para { >> =C2=A0 =C2=A0 =C2=A0 content: Inlines[1] { >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 [1] Str "Text" >> =C2=A0 =C2=A0 =C2=A0 } >> =C2=A0 =C2=A0 } >> =C2=A0 } >> =C2=A0 meta: Meta {} >> } >> (#) meta Meta {} >> (#) blocks Blocks[1] {[1] Para {content: Inlines[1] {[1] Str "Text"}}} >> (#) block Para {content: Inlines[1] {[1] Str "Text"}} >> (#) inlines Inlines[1] {[1] Str "Text"} >> (#) inline Str "Text" >> >> The writer: >> >> local logging =3D require 'logging' >> >> local function report(label, elem) >> =C2=A0 =C2=A0 logging.temp(label, elem) >> end >> >> -- 'typewise' (default) or 'topdown' >> local traverse =3D 'topdown' >> >> function Writer (doc, opts) >> =C2=A0 =C2=A0 local filter =3D { >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 traverse =3D traverse, >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Inline =3D function(inline) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('inline', inline) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 end, >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Inlines=3D function(inlines) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('inlines', inlines) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 end, >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Block =3D function(block) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('block', block) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 end, >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Blocks =3D function(blocks) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('blocks', blocks) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 end, >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Meta =3D function(meta) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('meta', meta) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 end, >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Pandoc =3D function(doc) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('doc', doc) >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 end, >> =C2=A0 =C2=A0 } >> =C2=A0 =C2=A0 return pandoc.write(doc:walk(filter), 'html', opts) >> end >> > Thank you for your thoughtful response. I realize I have used the term 'f= ilter' and 'writer' cavalierly. I have a "slightly" complicated layout I wa= nt to output from the writer and my thought right now is that I should try = to add the

and

in the right places in a filter and then let th= e writer just output the resulting html. > > I may have to traverse the AST several times in my filter to accomplish t= he result since multiple

need to be added at different levels t= o achieve the desired output. > > I just downloaded your logging filter to aid in the development and am al= so working on formalizing the rules for adding

. > > I spent some more time learning more about writing filters and have made so= me progress. I think the entire logic for adding

to achieve the desired layo= ut might be doable in the filter and most of it seems to be working. One thing I found is that when an image is included using the following syn= tax ![test](https://www.somedomain.tld/test.jpg) pandoc wraps the element in

which I think I don't= want/need. How can I get rid of

wrapped around elements? At the very = least I want got get rid of some text I do not need inside the

element? --=20 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 e= mail 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/992af9a4-285c-a20f-56de-347ea88f021f%40meddatainc.com. --------------D2ACCC6BE61243FCF5B40674 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On 06/06/2023 03:14 PM, H wrote:

On 06/01/2023 04:34 AM, 'William Lupton' via pandoc-discuss wrote:

Am I correct in thinking that when you say "filter" here, you really mean "writer"?

In filters, you can use the 'traverse' field to force top-down traversal. See https://pandoc.org/lua-filters.html#= traversal-order

In writers, you can choose to call doc:walk(), which will honour 'traverse'. See=C2=A0https://pandoc.org/custom-writers.ht= ml#example-modified-markdown-writer (and example below)

However, if you use=C2=A0pandoc.scaffolding.Writer (as I thi= nk you are?) then I suspect that you can't control the traversal order (but I'm not sure that it makes sense to do so, because, for example, surely you always want the contents of a <div> to have been traversed before you add '<div>' and '</div>'?).

With the custom writer shown below, and with an input file that consists of the single line 'Text' (and using my logging module), you get this with the default 'typewise' traversal:

(#) inline Str "Text"
(#) inlines Inlines[1] {[1] Str "Text"}
(#) block Para {content: Inlines[1] {[1] Str "Text"}}
(#) blocks Blocks[1] {[1] Para {content: Inlines[1] {[1] Str "Text"}}}
(#) meta Meta {}
(#) doc Pandoc {
=C2=A0 blocks: Blocks[1] {
=C2=A0 =C2=A0 [1] Para {
=C2=A0 =C2=A0 =C2=A0 content: Inlines[1] {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 [1] Str "Text"
=C2=A0 =C2=A0 =C2=A0 }
=C2=A0 =C2=A0 }
=C2=A0 }
=C2=A0 meta: Meta {}
}

...and this with 'topdown' traversal:

(#) doc Pandoc {
=C2=A0 blocks: Blocks[1] {
=C2=A0 =C2=A0 [1] Para {
=C2=A0 =C2=A0 =C2=A0 content: Inlines[1] {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 [1] Str "Text"
=C2=A0 =C2=A0 =C2=A0 }
=C2=A0 =C2=A0 }
=C2=A0 }
=C2=A0 meta: Meta {}
}
(#) meta Meta {}
(#) blocks Blocks[1] {[1] Para {content: Inlines[1] {[1] Str "Text"}}}
(#) block Para {content: Inlines[1] {[1] Str "Text"}}
(#) inlines Inlines[1] {[1] Str "Text"}
(#) inline Str "Text"

The writer:

local logging =3D require 'logging'=

local function report(label, elem)
=C2=A0 =C2=A0 logging.temp(label, elem)
end

-- 'typewise' (default) or 'topdown'
local traverse =3D 'topdown'

function Writer (doc, opts)
=C2=A0 =C2=A0 local filter =3D {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 traverse =3D traverse,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Inline =3D function(inline)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('inline', in= line)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 end,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Inlines=3D function(inlines)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('inlines', i= nlines)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 end,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Block =3D function(block)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('block', blo= ck)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 end,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Blocks =3D function(blocks)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('blocks', bl= ocks)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 end,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Meta =3D function(meta)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('meta', meta= )
=C2=A0 =C2=A0 =C2=A0 =C2=A0 end,
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pandoc =3D function(doc)
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 report('doc', doc)<= br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 end,
=C2=A0 =C2=A0 }
=C2=A0 =C2=A0 return pandoc.write(doc:walk(filter), 'html', o= pts)
end

Thank you for your thoughtful response. I realize I have used the term 'filter' and 'writer' cavalierly. I have a "slightly" complicated layout I want to output from the writer and my thought right now is that I should try to add the <div> and </div> in the right places in a filter and then let the writer just output the resulting html.

I may have to traverse the AST several times in my filter to accomplish the result since multiple <div></div> need to be added at different levels to achieve the desired output.

I just downloaded your logging filter to aid in the development and am also working on formalizing the rules for adding <div></div>.

I spent some more time learning more about writing filters and have made some progress.

I think the entire logic for adding <div></div> to achieve the desired layout might be doable in the filter and most of it seems to be working.

One thing I found is that when an image is included using the following syntax
![test](https://www.somedomain.tld/test.jpg)
pandoc wraps the <image> element in <figure></figure> which I think I don't want/need.

How can I get rid of <figure> wrapped around <image> elements? At the very least I want got get rid of <figurecaption>some text I do not need</figurecaption> inside the <figure></figure> element?

--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/ms= gid/pandoc-discuss/992af9a4-285c-a20f-56de-347ea88f021f%40meddatainc.com.
--------------D2ACCC6BE61243FCF5B40674--