From: ThomasH <therch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: What is the point of isBlockElement in the JATS reader?
Date: Fri, 19 May 2023 00:50:21 -0700 (PDT) [thread overview]
Message-ID: <e8dfa46a-1f69-4fa6-a412-6751e2250cacn@googlegroups.com> (raw)
In-Reply-To: <af881a3e-4f9a-4644-87b5-aaf93e6e959an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1346 bytes --]
It appears that all element types first listed are then exempted again via
the `inlinetags` list, except the `p` type. This looks indeed like a very
complicated way to come up with a list of only `p`. - A bug? Or maybe an
attempt to conform to a common pattern in Pandoc to list candidates first
and then subtract them again if necessary? I have no knowledge of JATS so I
cannot comment on semantics. Is there some kind of ambiquity that e.g. the
`address` element can appear both as a block *and* inline element?
On Friday, May 19, 2023 at 1:47:46 AM UTC+2 Julia Diaz wrote:
> I just realised this function produces TRUE if the name of the element is
> "p", false otherwise. Why do we need a 126 lines
> <https://github.com/jgm/pandoc/blob/16f28ef5e945f3be14e05afb7d91f8adca18e49a/src/Text/Pandoc/Readers/JATS.hs#L106-L132>
> to do the same as:
>
> qName (elName e) == p
>
> What am I missing?
>
--
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/e8dfa46a-1f69-4fa6-a412-6751e2250cacn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2685 bytes --]
next prev parent reply other threads:[~2023-05-19 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 23:47 Julia Diaz
[not found] ` <af881a3e-4f9a-4644-87b5-aaf93e6e959an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-19 7:50 ` ThomasH [this message]
[not found] ` <e8dfa46a-1f69-4fa6-a412-6751e2250cacn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-19 12:27 ` Albert Krewinkel
[not found] ` <87cz2wo61j.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2023-05-19 22:22 ` Julia Diaz
[not found] ` <a71b20c8-7a6c-41ac-9af0-141b908111f7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-20 17:00 ` Julia Diaz
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=e8dfa46a-1f69-4fa6-a412-6751e2250cacn@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).