From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/29373 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Milan Bracke Newsgroups: gmane.text.pandoc Subject: Re: docx parsing bug: nested fldChar fields are interpreted incorrectly Date: Thu, 14 Oct 2021 02:33:36 -0700 (PDT) Message-ID: <50bcbdc6-8d4b-49c1-badb-f35fb968112dn@googlegroups.com> References: <2f5489af-f5a9-4ea4-9155-9f85c4808756n@googlegroups.com> <9bdb337d-fa68-4c66-8f5c-d4fa81547953n@googlegroups.com> <24273fbf-2ce9-4c26-886b-50d504cb7b05n@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1022_275062084.1634204016369" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14862"; mail-complaints-to="usenet@ciao.gmane.io" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBDM4NA6G6UGRB4PST6FQMGQE2EZZW2Q-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Thu Oct 14 11:33:40 2021 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane-mx.org Original-Received: from mail-oi1-f184.google.com ([209.85.167.184]) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1max7M-0003fc-3v for gtp-pandoc-discuss@m.gmane-mx.org; Thu, 14 Oct 2021 11:33:40 +0200 Original-Received: by mail-oi1-f184.google.com with SMTP id o62-20020acaf041000000b00276562d5a75sf3309949oih.13 for ; Thu, 14 Oct 2021 02:33:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20210112; h=sender:date:from:to:message-id:in-reply-to:references:subject :mime-version:x-original-sender:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:list-subscribe :list-unsubscribe; bh=SkYr3dN4aBYZ7B7BtC6bam0mhz7CcfXP04BSHqzL0Po=; b=QP/cDrH9hVjyZPTT/aLUXDzJPRfyCazG1RY42nufCx4Q70KaVNjg4mgESXOrPVnlon cWi3j3Cj6FF7cfFmesuPlkCMi8PFerp7xNPDeKL/dRBnXm653GCSwjE5EW9NbPIH8YRQ tGX2bBy9MEr7MdZvSJIgM+edhXizYOCdtnfAhS+uh5VGROpMgJwUOj6bBUWyl2zfB/uh CbitBWhLNErDQDiGvEYXxpTtjnJ+TUKqKXCp8LcdwWeKrps2MZQ4ASASCR8JPkGeZiI/ jQlcx5ec+Q207bAXWiw/lPg/wI5uOWF4JPnV6v1nrdgK2C88S4iV0Y9+iaOJBWfyA6Sw csFQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:message-id:in-reply-to:references:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=SkYr3dN4aBYZ7B7BtC6bam0mhz7CcfXP04BSHqzL0Po=; b=DxMvGUwBCLMLzfKSJ4vg7S4TvR83Izur7MNZ2RtXFNv/qRwBRzmGIN2c5RSfbXOayC v8Nlp3y16em6Lg5L6STKDqmdz7C0/PfCdS00xpTGEj/1H548yv6T+ByYXOQif6xS5VE7 p5K0DI//tbjjOtCsLIZSlytzKP8Jh9lT8QDSHGiCaCDaV+BTSrPz8ZEhWGD6zTLf7qMt w9GNyNKjrxEEfOHtp9WBLI6e+KMUM8fccWxU78PjXQXl+ZJULsY1+VQ8mU/5ekUdUpf5 4gCl8UaA/dc5hyJW/68D93HdiYUtb4f1Kd5YIvQmXhM8RjLXTaXp8DvUmhqoF+KVyKUl Yodg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=sender:x-gm-message-state:date:from:to:message-id:in-reply-to :references:subject:mime-version:x-original-sender:reply-to :precedence:mailing-list:list-id:x-spam-checked-in-group:list-post :list-help:list-archive:list-subscribe:list-unsubscribe; bh=SkYr3dN4aBYZ7B7BtC6bam0mhz7CcfXP04BSHqzL0Po=; b=01p0bElX6iDcv4cNH6Pu/HlbbT+At6cmECPQvq9Ha0+f4n3PZFiscGtKFAv4gKs+bE MWfm6VqQqkuIalqpXoE9utBG+RPNFeQA4OHAjMrl4bgfWFbJfhcgoq6WCiXSI+0DdRU/ 1mx13id0iPssRwnzsuE5jTv5k35rpf+ItgsSLEdhVvRCXsDjlT+3OL/t31w24bRUaFG1 bL20FkViUkFEwTBJGc3c6ZuPPalONQJxAXSqE0cwA1e6d2EilI23WtmQzbpWV4l6yj12 32mo+iKoxToUlEjDg1XdKNYKcJJxdMuuff7tLHfa4Flta+JHjgDvtpTKNHDj3wxopFog JMIA== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: AOAM5312xVCC0NlV3guKoHluavH+AFp4sWqEUnh5Mi9WOUwPGUCNaja4 4R2NQ+/81ANZMb3qk00M+C8= X-Google-Smtp-Source: ABdhPJzIL+8wDoOkgTQhbfXaVYURjt5rBFW6ffSdC6E3WEWu+9SPe6hhDDRFrTtZ12MUc3H5zO/A2Q== X-Received: by 2002:aca:6c2:: with SMTP id 185mr1806262oig.31.1634204018569; Thu, 14 Oct 2021 02:33:38 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:a9d:4597:: with SMTP id x23ls10141ote.1.gmail; Thu, 14 Oct 2021 02:33:37 -0700 (PDT) X-Received: by 2002:a05:6830:1acc:: with SMTP id r12mr1526824otc.154.1634204017097; Thu, 14 Oct 2021 02:33:37 -0700 (PDT) In-Reply-To: X-Original-Sender: milan.bracke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Xref: news.gmane.io gmane.text.pandoc:29373 Archived-At: ------=_Part_1022_275062084.1634204016369 Content-Type: multipart/alternative; boundary="----=_Part_1023_1642519140.1634204016369" ------=_Part_1023_1642519140.1634204016369 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Jesse, I hope you had a good summer. Do you have time to look at my pull request= =20 in the coming weeks? I'm now using a fork of Pandoc to have this fix and I have to rebase every= =20 time something useful is done in the main repo, so I would really like to have this fix merged. Best, Milan On Thursday, July 15, 2021 at 4:47:19 PM UTC+2 Jesse Rosenthal wrote: > Hi Milan, > > Thanks for the heads up. Honestly just summer craziness: visiting family= =20 > for the first time in almost two years, shuttling the kids around. Life= =20 > stuff. I'll take a look at it ASAP. > > Best, > Jesse > > ________________________________________ > From: pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org on behalf= =20 > of Milan Bracke > Sent: Thursday, July 15, 2021 10:43 AM > To: pandoc-discuss > Subject: Re: docx parsing bug: nested fldChar fields are interpreted=20 > incorrectly > > Hi all, > > I've had this pull request open for more than 3 weeks now:=20 > https://github.com/jgm/pandoc/pull/7401 > Is there a reason it's not getting any reaction? I'd be happy to improve= =20 > or explain it. If I've done something > wrong, I'd like to know, so I can fix it. > > Best, > Milan > > On Thursday, June 17, 2021 at 8:42:48 AM UTC+2 Milan Bracke wrote: > Hi Jesse, > > Thanks for the feedback. I'll ping you when making the PR. Most of my cod= e=20 > seems to work so far, but I still > have some trouble with the fact that the fields now need to contain=20 > ParParts instead of Runs. It's harder to > match all the cases and treat them correctly. I'll try some more and let= =20 > you know how it goes. > > Best, > Milan > On Wednesday, June 16, 2021 at 4:21:05 PM UTC+2 Jesse Rosenthal wrote: > Hi Milan, > > I wrote the original fldChar code (and that comment) and I figured it=20 > would have to evolve as further requirements became necessary. If nesting= =20 > is a requirement, a stack instead of a toggle seems appropriate. > > As far as crossing paragraphs goes -- your approach seems right (and=20 > similar to how we've dealt with similar issues like comments crossing=20 > paragraphs in docx parsing). > > I'd be happy to take a look and offer comments/feedback on your code. Jus= t=20 > make sure to ping me (@jkr) on your PRs. > > Best, > Jesse > > ________________________________________ > From: pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org on behalf= =20 > of Milan Bracke > Sent: Wednesday, June 16, 2021 5:33 AM > To: pandoc-discuss > Subject: Re: docx parsing bug: nested fldChar fields are interpreted=20 > incorrectly > > I can't fix this without at least some feedback. It's a complex issue and= =20 > the fix will take some time, so I need to at least know that my proposed= =20 > solution > seems good and would be accepted if implemented correctly. > > On Tuesday, June 15, 2021 at 8:38:30 AM UTC+2 Milan Bracke wrote: > I've encountered a new problem. A fldChar field can span multiple=20 > paragraphs, but it doesn't have to start at the beginning of the first on= e. > Because of this, a field across multiple paragraphs will merge those=20 > paragraphs. > There is no way to represent this exactly in the pandoc model I think. So= =20 > my current solution is to have different fields with the same field > info in the different paragraphs. This can at least make the hyperlink=20 > fields work and I think it will work for the other fields we might add in > the future as well (I've checked the list). > What do you think about this ? > > On Monday, June 14, 2021 at 9:17:13 AM UTC+2 Milan Bracke wrote: > For those who don't know fldChar fields, this comment from the docx parse= =20 > code (parse.hs, starting on line 825) explains it: > > fldChar fields work by first > having a in a run, then a run with > , then a run, then the > content runs, and finally a run. For > example (omissions and my comments in brackets): > > > [...] > > > > [...] > HYPERLINK [hyperlink url] > > > [...] > > > > [...] > Foundations of Analysis, 2nd Edition > > > [...] > > > > The current way of parsing fldChar fields doesn't take into account that= =20 > they can be nested. So the end of the nested flcChar field will be=20 > interpreted as the end of the surrounding one. This could for example lea= d=20 > to a hyperlink that ends too soon. See attached example for a docx that= =20 > demonstrates this. > > I propose to fix this by turning the fldChar state into a stack, so that = a=20 > field can be started and ended inside other fields. I will include this i= n=20 > my pull request for PAGEREF fields that I announced here a while ago, sin= ce=20 > they are related. > > -- > You received this message because you are subscribed to the Google Groups= =20 > "pandoc-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an= =20 > email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>. > To view this discussion on the web visit=20 > https://groups.google.com/d/msgid/pandoc-discuss/9bdb337d-fa68-4c66-8f5c-= d4fa81547953n%40googlegroups.com > < > https://nam02.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgroup= s.google.com%2Fd%2Fmsgid%2Fpandoc-discuss%2F9bdb337d-fa68-4c66-8f5c-d4fa815= 47953n%2540googlegroups.com&data=3D04%7C01%7Cjrosenthal%40jhu.edu%7Ca0b9fef= 0818d4fa2010808d9479efa08%7C9fa4f438b1e6473b803f86f8aedf0dec%7C0%7C0%7C6376= 19570850832949%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIi= LCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3DyihkvC%2B7Le7l00nWwyXnOyOmASI= ibuFvMDgLIXStUSc%3D&reserved=3D0 > >< > https://nam02.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgroup= s.google.com%2Fd%2Fmsgid%2Fpandoc-discuss%2F9bdb337d-fa68-4c66-8f5c-d4fa815= 47953n%2540googlegroups.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data= =3D04%7C01%7Cjrosenthal%40jhu.edu%7C3013bb2b353d4b73a4dd08d930a9dbd8%7C9fa4= f438b1e6473b803f86f8aedf0dec%7C0%7C0%7C637594329240701072%7CUnknown%7CTWFpb= GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7= C3000&sdata=3D8fxpTInSSkpzMwmvDK0BYRHtKx%2BArUEcX7BLQoBE7qo%3D&reserved=3D0 > < > https://nam02.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgroup= s.google.com%2Fd%2Fmsgid%2Fpandoc-discuss%2F9bdb337d-fa68-4c66-8f5c-d4fa815= 47953n%2540googlegroups.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data= =3D04%7C01%7Cjrosenthal%40jhu.edu%7Ca0b9fef0818d4fa2010808d9479efa08%7C9fa4= f438b1e6473b803f86f8aedf0dec%7C0%7C0%7C637619570850842907%7CUnknown%7CTWFpb= GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7= C3000&sdata=3DIYMIxCLKxoONu7qa9IQViRyjj%2FaOVY8x%2FuHlI2oMfXQ%3D&reserved= =3D0 > >>. > > -- > You received this message because you are subscribed to the Google Groups= =20 > "pandoc-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an= =20 > email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>. > To view this discussion on the web visit=20 > https://groups.google.com/d/msgid/pandoc-discuss/24273fbf-2ce9-4c26-886b-= 50d504cb7b05n%40googlegroups.com > < > https://nam02.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgroup= s.google.com%2Fd%2Fmsgid%2Fpandoc-discuss%2F24273fbf-2ce9-4c26-886b-50d504c= b7b05n%2540googlegroups.com%3Futm_medium%3Demail%26utm_source%3Dfooter&data= =3D04%7C01%7Cjrosenthal%40jhu.edu%7Ca0b9fef0818d4fa2010808d9479efa08%7C9fa4= f438b1e6473b803f86f8aedf0dec%7C0%7C0%7C637619570850852858%7CUnknown%7CTWFpb= GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7= C3000&sdata=3D%2BFQ5SkpbfzgZ7yLWGIi9uTHBuMaN9nBZzA%2Ffzwt4XnU%3D&reserved= =3D0 > >. > --=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/50bcbdc6-8d4b-49c1-badb-f35fb968112dn%40googlegroups.com. ------=_Part_1023_1642519140.1634204016369 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Jesse,

I hope you had a good summer. Do yo= u have time to look at my pull request in the coming weeks?
I'm n= ow using a fork of Pandoc to have this fix and I have to rebase every time = something useful is done
in the main repo, so I would really like= to have this fix merged.

Best,
Mila= n

On Thursday, July 15, 2021 at 4:47:19 PM UTC+2 Jesse Rosenthal wrote:=
Hi Milan,

Thanks for the heads up. Honestly just summer craziness: visiting famil= y for the first time in almost two years, shuttling the kids around. Life s= tuff. I'll take a look at it ASAP.

Best,
Jesse

________________________________________
From: pandoc-...@googlegroup= s.com <pandoc-...@googleg= roups.com> on behalf of Milan Bracke <milan....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Sent: Thursday, July 15, 2021 10:43 AM
To: pandoc-discuss
Subject: Re: docx parsing bug: nested fldChar fields are interpreted in= correctly

Hi all,

I've had this pull request open for more than 3 weeks now: https://github.com/jg= m/pandoc/pull/7401
Is there a reason it's not getting any reaction? I'd be happy t= o improve or explain it. If I've done something
wrong, I'd like to know, so I can fix it.

Best,
Milan

On Thursday, June 17, 2021 at 8:42:48 AM UTC+2 Milan Bracke wrote:
Hi Jesse,

Thanks for the feedback. I'll ping you when making the PR. Most of = my code seems to work so far, but I still
have some trouble with the fact that the fields now need to contain Par= Parts instead of Runs. It's harder to
match all the cases and treat them correctly. I'll try some more an= d let you know how it goes.

Best,
Milan
On Wednesday, June 16, 2021 at 4:21:05 PM UTC+2 Jesse Rosenthal wrote:
Hi Milan,

I wrote the original fldChar code (and that comment) and I figured it w= ould have to evolve as further requirements became necessary. If nesting is= a requirement, a stack instead of a toggle seems appropriate.

As far as crossing paragraphs goes -- your approach seems right (and si= milar to how we've dealt with similar issues like comments crossing par= agraphs in docx parsing).

I'd be happy to take a look and offer comments/feedback on your cod= e. Just make sure to ping me (@jkr) on your PRs.

Best,
Jesse

________________________________________
From: pandoc-...@googlegroup= s.com <pandoc-...@googleg= roups.com> on behalf of Milan Bracke <milan....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Sent: Wednesday, June 16, 2021 5:33 AM
To: pandoc-discuss
Subject: Re: docx parsing bug: nested fldChar fields are interpreted in= correctly

I can't fix this without at least some feedback. It's a complex= issue and the fix will take some time, so I need to at least know that my = proposed solution
seems good and would be accepted if implemented correctly.

On Tuesday, June 15, 2021 at 8:38:30 AM UTC+2 Milan Bracke wrote:
I've encountered a new problem. A fldChar field can span multiple p= aragraphs, but it doesn't have to start at the beginning of the first o= ne.
Because of this, a field across multiple paragraphs will merge those pa= ragraphs.
There is no way to represent this exactly in the pandoc model I think. = So my current solution is to have different fields with the same field
info in the different paragraphs. This can at least make the hyperlink = fields work and I think it will work for the other fields we might add in
the future as well (I've checked the list).
What do you think about this ?

On Monday, June 14, 2021 at 9:17:13 AM UTC+2 Milan Bracke wrote:
For those who don't know fldChar fields, this comment from the docx= parse code (parse.hs, starting on line 825) explains it:

fldChar fields work by first
having a <w:fldChar fldCharType=3D"begin"> in a run, th= en a run with
<w:instrText>, then a <w:fldChar fldCharType=3D"separate&= quot;> run, then the
content runs, and finally a <w:fldChar fldCharType=3D"end"= > run. For
example (omissions and my comments in brackets):

<w:r>
[...]
<w:fldChar w:fldCharType=3D"begin"/>
</w:r>
<w:r>
[...]
<w:instrText xml:space=3D"preserve"> HYPERLINK [hyperli= nk url] </w:instrText>
</w:r>
<w:r>
[...]
<w:fldChar w:fldCharType=3D"separate"/>
</w:r>
<w:r w:rsidRPr=3D[...]>
[...]
<w:t>Foundations of Analysis, 2nd Edition</w:t>
</w:r>
<w:r>
[...]
<w:fldChar w:fldCharType=3D"end"/>
</w:r>

The current way of parsing fldChar fields doesn't take into account= that they can be nested. So the end of the nested flcChar field will be in= terpreted as the end of the surrounding one. This could for example lead to= a hyperlink that ends too soon. See attached example for a docx that demon= strates this.

I propose to fix this by turning the fldChar state into a stack, so tha= t a field can be started and ended inside other fields. I will include this= in my pull request for PAGEREF fields that I announced here a while ago, s= ince they are related.

--
You received this message because you are subscribed to the Google Grou= ps "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send = an email to pandoc-discus...@goo= glegroups.com<mailto:pand= oc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/9bdb337d-fa= 68-4c66-8f5c-d4fa81547953n%40googlegroups.com<https://nam02.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2= Fgroups.google.com%2Fd%2Fmsgid%2Fpandoc-discuss%2F9bdb337d-fa68-4c66-8f5c-d= 4fa81547953n%2540googlegroups.com&data=3D04%7C01%7Cjrosenthal%40jhu.edu= %7Ca0b9fef0818d4fa2010808d9479efa08%7C9fa4f438b1e6473b803f86f8aedf0dec%7C0%= 7C0%7C637619570850832949%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIj= oiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3DyihkvC%2B7Le7l0= 0nWwyXnOyOmASIibuFvMDgLIXStUSc%3D&reserved=3D0><https://nam02.safelinks.protection.outl= ook.com/?url=3Dhttps%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fpandoc-discuss= %2F9bdb337d-fa68-4c66-8f5c-d4fa81547953n%2540googlegroups.com%3Futm_medium%= 3Demail%26utm_source%3Dfooter&data=3D04%7C01%7Cjrosenthal%40jhu.edu%7C3= 013bb2b353d4b73a4dd08d930a9dbd8%7C9fa4f438b1e6473b803f86f8aedf0dec%7C0%7C0%= 7C637594329240701072%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2= luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3D8fxpTInSSkpzMwmvDK0= BYRHtKx%2BArUEcX7BLQoBE7qo%3D&reserved=3D0<https://nam02.safelinks.protection.outl= ook.com/?url=3Dhttps%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fpandoc-discuss= %2F9bdb337d-fa68-4c66-8f5c-d4fa81547953n%2540googlegroups.com%3Futm_medium%= 3Demail%26utm_source%3Dfooter&data=3D04%7C01%7Cjrosenthal%40jhu.edu%7Ca= 0b9fef0818d4fa2010808d9479efa08%7C9fa4f438b1e6473b803f86f8aedf0dec%7C0%7C0%= 7C637619570850842907%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2= luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3DIYMIxCLKxoONu7qa9IQ= ViRyjj%2FaOVY8x%2FuHlI2oMfXQ%3D&reserved=3D0>>.

--
You received this message because you are subscribed to the Google Grou= ps "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send = an email to pandoc-discus...@goo= glegroups.com<mailto:pand= oc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/24273fbf-2c= e9-4c26-886b-50d504cb7b05n%40googlegroups.com<https://nam02.safelinks.protection.outlook= .com/?url=3Dhttps%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fpandoc-discuss%2F= 24273fbf-2ce9-4c26-886b-50d504cb7b05n%2540googlegroups.com%3Futm_medium%3De= mail%26utm_source%3Dfooter&data=3D04%7C01%7Cjrosenthal%40jhu.edu%7Ca0b9= fef0818d4fa2010808d9479efa08%7C9fa4f438b1e6473b803f86f8aedf0dec%7C0%7C0%7C6= 37619570850852858%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luM= zIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3D%2BFQ5SkpbfzgZ7yLWGIi9= uTHBuMaN9nBZzA%2Ffzwt4XnU%3D&reserved=3D0>.

--
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= /msgid/pandoc-discuss/50bcbdc6-8d4b-49c1-badb-f35fb968112dn%40googlegroups.= com.
------=_Part_1023_1642519140.1634204016369-- ------=_Part_1022_275062084.1634204016369--