From: ThomasH <therch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Lua Filter: How to write a filter function for a Cell of a Table
Date: Tue, 16 May 2023 05:59:31 -0700 (PDT) [thread overview]
Message-ID: <e6ba297b-1a4b-42cc-adaa-1b831340f8c4n@googlegroups.com> (raw)
In-Reply-To: <4e77e8b9-2ca9-4da0-8c5c-c3e1cb005e50n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1726 bytes --]
Ok, I implemented a solution going off of the Table filter. This is the
basic pattern:
function Table(table)
for ibody=1, #table.bodies do
local tbody = table.bodies[ibody]
for irow=1, #tbody.body do
local row = tbody.body[irow]
for icell=1, #row.cells do
local cell = row.cells[icell]
for iblock=1, #cell.contents do
cell.contents[iblock] =
cell.contents[iblock]:walk(some_filter_map) -- cell blocks can be walk'ed
again
...
end
This works, but is ugly because of all those nested loops.
I wonder is there a specific reason to exempt the element components like
rows and cells from the normal visitor pattern?
On Monday, May 15, 2023 at 10:18:38 AM UTC+2 ThomasH wrote:
> I want to modify how table cells are translated. I started out like with
> other AST types, e.g.
>
> function Cell(cell)
> ... (do something with cell)
> end
>
> This function is never called, although the input document contains a
> table with cells.
>
> I assume, element components like cells are treated differently (although
> they seem to appear in the AST like other AST nodes).
>
> What is the correct way to write filter functions for element components?
>
> Thanks, T.
>
--
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/e6ba297b-1a4b-42cc-adaa-1b831340f8c4n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2515 bytes --]
prev parent reply other threads:[~2023-05-16 12:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 8:18 ThomasH
[not found] ` <4e77e8b9-2ca9-4da0-8c5c-c3e1cb005e50n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-16 12:59 ` ThomasH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e6ba297b-1a4b-42cc-adaa-1b831340f8c4n@googlegroups.com \
--to=therch-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).