From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/32248 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "'Peter Vedal Utnes' via pandoc-discuss" Newsgroups: gmane.text.pandoc Subject: Re: Error caused by document length Date: Mon, 27 Feb 2023 08:49:45 -0800 (PST) Message-ID: References: <7ed278f7-071b-4bcc-9f9a-e9dd5c09ee55n@googlegroups.com> <8f11cfaf-7c36-4cc6-9866-aa3741d965a4n@googlegroups.com> <4bd152b5-32f7-4f4c-9a9b-0d20afebea84n@googlegroups.com> <0AFB3E23-B7C1-49E8-9F8A-12716F6A2C40@gmail.com> <20942a45-0995-4a50-888a-cf25e9895920n@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_4856_1011065552.1677516585685" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30482"; mail-complaints-to="usenet@ciao.gmane.io" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBCWNVA7FUIMRBKV66OPQMGQEZYHO7NI-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mon Feb 27 17:49:50 2023 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane-mx.org Original-Received: from mail-qv1-f59.google.com ([209.85.219.59]) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pWghC-0007kX-Ak for gtp-pandoc-discuss@m.gmane-mx.org; Mon, 27 Feb 2023 17:49:50 +0100 Original-Received: by mail-qv1-f59.google.com with SMTP id s18-20020a0cf792000000b00572c04240f1sf3639075qvn.8 for ; Mon, 27 Feb 2023 08:49:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20210112; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to:x-original-sender :mime-version:subject:references:in-reply-to:message-id:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=1m/+Sm+7XTmt9G7TWV1cfy8gMH03iXBXeCpNiW54w84=; b=njRNNIdm0rOym9e+P87JUeecbgS0+k/5PNW9myrna112DfnXf8lJWLt8Co1IxQBSxe ha4dMwspgayfafk5l0NaTdKpCsyk2NLIT5ggIoNZjI4Nb2mDdiHXVHAcgZeW5qsiHJRq nMNxpyyRuKonXf9JLnKK2QwsB1MYNpo2lXmdt2OxXPLoZzPa0k9uUoNGdbY4aquYHe0d 3b+RPZWBPf4nSB2Xvlu47R6gFuzdPIBJcH5E/aqgRXp2nib5QYoZo5CLe3C8WWnGQnwz 6i/zj+gI4K2dDAZs4b8Rou+1H2J5G8O1ME/EiV5OI3yW8hgbmtfixvPcLsMwkPDGaTAP D6zw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :x-spam-checked-in-group:list-id:mailing-list:precedence:reply-to :x-original-sender:mime-version:subject:references:in-reply-to :message-id:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=1m/+Sm+7XTmt9G7TWV1cfy8gMH03iXBXeCpNiW54w84=; b=c6fBSnG1yoT5mAeSJkqtYQjE88GjlsaWi1h3qUV34V/E7SI2gurZ3n7ccVQguItEx4 wBnCzxUthCUnM3M3msBHY0hgnDW8Lo3eBmP0ZDNa9jo+h8HP3ugGzlW8CjWBK20cR7BU P6o4MWTkJG7kHxs0e7Cmqr0PSMZPEjitt6bKrbvNXOO5gGiMFQe4n3Mi1RADL9obpDHK pVQOBBO2dFTdDk8Y2WEkZQgOYh+PKQgqYK6HrhwMvhyfpij0u5U03mwMjNMcVozOoIMn nUNGl68bU1rp33edveIfjs4VKW4NmjDSeT4CIJKH6PBhB9wvH8eotAQbgkkPza0KFDhP ptLA== X-Gm-Message-State: AO0yUKUMeHKslYo+NsZUAGE1Zr9GR/e/h3deV8+9V6NmDT4JaHzJTmh1 6h+ZUdIn+dBc6nASOMKOlSA= X-Google-Smtp-Source: AK7set+ToW3Xmc+WvHjf8Gs+Bh1kpVbRHMKFGpFbdZvpRD+9SlgV/PDYzpcjdUMlJyDewhR9Wl3KUw== X-Received: by 2002:a05:620a:840a:b0:742:ca67:145 with SMTP id pc10-20020a05620a840a00b00742ca670145mr122770qkn.4.1677516589075; Mon, 27 Feb 2023 08:49:49 -0800 (PST) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:ae9:c00b:0:b0:742:7031:69ef with SMTP id u11-20020ae9c00b000000b00742703169efls2076044qkk.11.-pod-prod-gmail; Mon, 27 Feb 2023 08:49:46 -0800 (PST) X-Received: by 2002:a05:620a:3608:b0:742:6e93:5122 with SMTP id da8-20020a05620a360800b007426e935122mr3242007qkb.15.1677516586290; Mon, 27 Feb 2023 08:49:46 -0800 (PST) In-Reply-To: X-Original-Sender: peter.v.utnes-hYqmg196XYc@public.gmane.org X-Original-From: Peter Vedal Utnes 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:32248 Archived-At: ------=_Part_4856_1011065552.1677516585685 Content-Type: multipart/alternative; boundary="----=_Part_4857_1618590406.1677516585685" ------=_Part_4857_1618590406.1677516585685 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable When I convert and try to publish a document with only the offending=20 sentences, it does indeed fail, Bastien. Even when the document is=20 otherwise empty. It is hard to see what might be causing this. I will have= =20 to continue the elimination down to the word, but I've been at this for=20 nine hours and it is getting late. Will do that tomorrow. Meanwhile, thanks= =20 for the help, all of you.=20 mandag 27. februar 2023 kl. 17:41:58 UTC+1 skrev Bastien DUMONT: > If you narrow down the document to the offending sentences (or only one o= f=20 > them), does bibi fail to read the resulting EPUB? Such minimal source and= =20 > EPUB documents would be easier to inspect, and the latter could even be= =20 > included in a bug report for bibi. > > Le Monday 27 February 2023 =C3=A0 08:22:34AM, 'Peter Vedal Utnes' via=20 > pandoc-discuss a =C3=A9crit : > > I have now done the elimination process, as suggested by Bastien, of=20 > replacing > > the working file, which was the EPUB of the research paper where I had= =20 > swapped > > paragraphs 2-10 with "test test test", with the original paragraphs fro= m=20 > the > > paper. It worked until I tried to restore a sentence in the middle of= =20 > paragraph > > 3, going from above, or paragraph 6, going from below. When I insert th= e=20 > next > > sentence in either end, the document fails to convert (in a manner=20 > readable by > > bibi epub viewer). There does not seem to be unicode characters that=20 > might > > interfere. I have ran the debugger you suggest, John ,and there are=20 > indeed > > errors (metadata not filled in and a missing tag end) but I fixing thes= e=20 > do not > > seem to work.=20 > >=20 > > Here are the seemingly innocuous sentences that fail from above and=20 > below, > > respectively: 1) Over years I have experienced much Bronze in the form= =20 > of > > articles in toll access (TA) journals that have been made freely=20 > available for > > reading =E2=80=93 not open access, but =E2=80=9CFree access=E2=80=9D as= some publishers call it.=20 > 2) One > > thing is to help editors to become aware of the issue, another is to fi= nd > > practical solutions for them to transition their scholarly content to O= A=20 > =E2=80=93 the > > rest of their content is really not of interest to us. > >=20 > > There seem to issues with a few other sentences in those 3 paragraphs= =20 > too, but > > I can't see a pattern.=20 > > Here is the article in question, though it is only the PDF galley, my= =20 > EPUB > > testing is on a private server:=20 > https://septentrio.uit.no/index.php/nopos/ > > article/view/6665 > >=20 > >=20 > >=20 > > mandag 27. februar 2023 kl. 17:08:31 UTC+1 skrev John MacFarlane: > >=20 > > You could try running epubcheck on the epub produced by pandoc, to see = if > > it points to anything. > >=20 > >=20 > > > On Feb 27, 2023, at 6:33 AM, 'Peter Vedal Utnes' via pandoc-discuss < > > pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> wrote: > > > > > > I just did some further testing, and replaced the sections that I wou= ld > > otherwise have removed with as many words and paragraphs, but no signs, > > only "test test test" etc. The document then works. So I was wrong abou= t > > the length: It must be some character or symbol producing the error (on= ly > > with pandoc, not other EPUB converters). Any idea how to further isolat= e > > it, or how to circumvent with a pandoc command or template? > > > > > > Thanks for the help so far, Bernardo. > > > > > > > > > > > > mandag 27. februar 2023 kl. 15:23:57 UTC+1 skrev Peter Vedal Utnes: > > > I am not sure what you mean by normalize in this context. I'll=20 > elaborate > > in case this is what you mean: In the interest of removing variables th= at > > might interfere with troubleshooting, I have copied the text from=20 > research > > papers (not just one, but a few), pasted it in notepad, copied and past= ed > > it back into a new word-file (this is more thorough than "clear > > formatting"), ran this "pure" file through pandoc and I get the error.= =20 > If I > > then randomly shorten the file, the error disappears. This is not the= =20 > case > > for my "test" file, but only for research papers, which is baffling. I= =20 > can > > only assume that pandoc responds to something like a character or in-te= xt > > references in particular contexts, or as was my original hypothesis, th= e > > number of lines or columns in the EPUB. > > > > > > mandag 27. februar 2023 kl. 15:17:10 UTC+1 skrev=20 > bernardov...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org: > > > Have you tried editing the original research paper in some minor way > > (adding or removing a couple of characters) and then running it? This i= s=20 > a > > completely wild guess, but maybe the text in the file is getting=20 > normalized > > upon editing them, whereas the original research paper still contains t= he > > unedited, unnormalized text. > > > > > > On Mon, Feb 27, 2023 at 10:48=E2=80=AFAM 'Peter Vedal Utnes' via=20 > pandoc-discuss < > > pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> wrote: > > > I thank you for the suggestion. It is proving somewhat hard to (dis) > > confirm. I have made a testfile with just the word "test" pasted over a= nd > > over again, with and without various formatting and with the same lengt= h=20 > or > > longer as the proper papers. This file consistently works. But when I > > attempt to do it with a regular research paper, it only works if I=20 > shorten > > it. Curiously, I can remove either half of the main text, or indeed > > sections here and there, randomly, and it works, but not with all of th= em > > present. I have combed it for special characters or tags, but cannot fi= nd > > any. > > > > > > mandag 27. februar 2023 kl. 13:49:58 UTC+1 skrev Bernardo C. D. A. > > Vasconcelos: > > > I do not know the answer to this problem in particular, but perhaps i= t=20 > is > > worth checking the main document and the bibliography for invisible=20 > control > > characters (e.g. `\X{A0}`). They tend to cause all sorts of strange > > problems that result in random error msgs. > > > > > > On Monday, February 27, 2023 at 8:16:20=E2=80=AFAM UTC-3 Peter Vedal = Utnes=20 > wrote: > > > We have a workflow in Open Journal Systems where we use Pandoc to=20 > convert > > word documents to EPUB, and then display them with an embedded EPUB app > > (Bibi). > > > > > > Our resulting EPUBs work fine with both debuggers and viewers like > > calibre. They work in Bibi, but only when they are reduced to a certain > > length. Whenever the files exceed approx 100 lines or 600 words, Bibi > > claims: > > > > > > TypeError: Cannot read properties of undefined (reading =E2=80=98getA= ttribute=E2=80=99) > > > > > > Meanwhile, the same documents works when converted to EPUB using othe= r > > converters, or when I reduce the length (length, not size in bytes-- I'= ve > > tried with graphics, still works). It suddenly works when I reduce the > > length by removing pure paragraph text, even though all the formatted > > elements (abstract, references, etc) are the same. > > > > > > I recognize that this problem is very specific to the interrelation > > pandoc <-> Bibi, but I'd be grateful for general troubleshooting > > suggestions. > > > > > > Thanks in advance, > > > > > > Peter > > > > > > > > > -- > > > You received this message because you are subscribed to a topic in th= e > > Google Groups "pandoc-discuss" group. > > > To unsubscribe from this topic, visit [1]https://groups.google.com/d/ > > topic/pandoc-discuss/hPUa1uWGS_k/unsubscribe. > > > To unsubscribe from this group and all its topics, send an email to= =20 > > pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit [2] > https://groups.google.com/d/ > > msgid/pandoc-discuss/ > > 4bd152b5-32f7-4f4c-9a9b-0d20afebea84n%40googlegroups.com. > > > > > > -- > > > You received this message because you are subscribed to the Google=20 > Groups > > "pandoc-discuss" group. > > > To unsubscribe from this group and stop receiving emails from it, sen= d=20 > an > > email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > To view this discussion on the web visit [3] > https://groups.google.com/d/ > > msgid/pandoc-discuss/ > > bc147d77-69c9-4e5d-82a6-e149f662a823n%40googlegroups.com. > >=20 > >=20 > > -- > > 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= =20 > an email > > to [4]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit [5] > https://groups.google.com/d/msgid/ > > pandoc-discuss/20942a45-0995-4a50-888a-cf25e9895920n%40googlegroups.com= . > >=20 > > References: > >=20 > > [1]=20 > https://groups.google.com/d/topic/pandoc-discuss/hPUa1uWGS_k/unsubscribe > > [2]=20 > https://groups.google.com/d/msgid/pandoc-discuss/4bd152b5-32f7-4f4c-9a9b-= 0d20afebea84n%40googlegroups.com > > [3]=20 > https://groups.google.com/d/msgid/pandoc-discuss/bc147d77-69c9-4e5d-82a6-= e149f662a823n%40googlegroups.com > > [4] mailto:pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > > [5]=20 > https://groups.google.com/d/msgid/pandoc-discuss/20942a45-0995-4a50-888a-= cf25e9895920n%40googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter > > --=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/a484697f-9076-4a13-acf1-a645fa611614n%40googlegroups.com. ------=_Part_4857_1618590406.1677516585685 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable When I convert and try to publish a document with only the offending senten= ces, it does indeed fail, Bastien. Even when the document is otherwise empt= y. It is hard to see what might be causing this. I will have to continue th= e elimination down to the word, but I've been at this for nine hours and it= is getting late. Will do that tomorrow. Meanwhile, thanks for the help, al= l of you.=C2=A0


mandag 27. februar 2023 kl. 17:41:5= 8 UTC+1 skrev Bastien DUMONT:
If you narrow down the document to the offending sentences= (or only one of them), does bibi fail to read the resulting EPUB? Such min= imal source and EPUB documents would be easier to inspect, and the latter c= ould even be included in a bug report for bibi.

Le Monday 27 February 2023 =C3=A0 08:22:34AM, 'Peter Vedal Utnes= 9; via pandoc-discuss a =C3=A9crit :
> I have now done the elimination process, as suggested by Bastien, = of replacing
> the working file, which was the EPUB of the research paper where I= had swapped
> paragraphs 2-10 with "test test test", with the original= paragraphs from the
> paper. It worked until I tried to restore a sentence in the middle= of paragraph
> 3, going from above, or paragraph 6, going from below. When I inse= rt the next
> sentence in either end, the document fails to convert (in a manner= readable by
> bibi epub viewer). There does not seem to be unicode characters th= at might
> interfere. I have ran the debugger you suggest, John ,and there ar= e indeed
> errors (metadata not filled in and a missing tag end) but I fixing= these do not
> seem to work.=C2=A0
>=20
> Here are the seemingly innocuous sentences that fail from above an= d below,
> respectively: 1)=C2=A0=C2=A0Over years I have experienced much Bro= nze in the form of
> articles in toll access (TA) journals that have been made freely a= vailable for
> reading =E2=80=93 not open access, but =E2=80=9CFree access=E2=80= =9D as some publishers call it. 2) One
> thing is to help editors to become aware of the issue, another is = to find
> practical solutions for them to transition their scholarly content= to OA =E2=80=93 the
> rest of their content is really not of interest to us.
>=20
> There seem to issues with a few other sentences in those 3 paragra= phs too, but
> I can't see a pattern.=C2=A0
> Here is the article in question, though it is only the PDF galley,= my EPUB
> testing is on a private server:=C2=A0https://septentrio.uit.no/index.php/nopos/=
> article/view/6665
>=20
>=20
>=20
> mandag 27. februar 2023 kl. 17:08:31 UTC+1 skrev John MacFarlane:
>=20
> You could try running epubcheck on the epub produced by pandoc= , to see if
> it points to anything.
>=20
>=20
> > On Feb 27, 2023, at 6:33 AM, 'Peter Vedal Utnes' = via pandoc-discuss <
> pandoc-...@googlegr= oups.com> wrote:
> >
> > I just did some further testing, and replaced the section= s that I would
> otherwise have removed with as many words and paragraphs, but = no signs,
> only "test test test" etc. The document then works. = So I was wrong about
> the length: It must be some character or symbol producing the = error (only
> with pandoc, not other EPUB converters). Any idea how to furth= er isolate
> it, or how to circumvent with a pandoc command or template?
> >
> > Thanks for the help so far, Bernardo.
> >
> >
> >
> > mandag 27. februar 2023 kl. 15:23:57 UTC+1 skrev Peter Ve= dal Utnes:
> > I am not sure what you mean by normalize in this context.= I'll elaborate
> in case this is what you mean: In the interest of removing var= iables that
> might interfere with troubleshooting, I have copied the text f= rom research
> papers (not just one, but a few), pasted it in notepad, copied= and pasted
> it back into a new word-file (this is more thorough than "= ;clear
> formatting"), ran this "pure" file through pand= oc and I get the error. If I
> then randomly shorten the file, the error disappears. This is = not the case
> for my "test" file, but only for research papers, wh= ich is baffling. I can
> only assume that pandoc responds to something like a character= or in-text
> references in particular contexts, or as was my original hypot= hesis, the
> number of lines or columns in the EPUB.
> >
> > mandag 27. februar 2023 kl. 15:17:10 UTC+1 skrev bernardov...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org:
> > Have you tried editing the original research paper in som= e minor way
> (adding or removing a couple of characters) and then running i= t? This is a
> completely wild guess, but maybe the text in the file is getti= ng normalized
> upon editing them, whereas the original research paper still c= ontains the
> unedited, unnormalized text.
> >
> > On Mon, Feb 27, 2023 at 10:48=E2=80=AFAM 'Peter Vedal= Utnes' via pandoc-discuss <
> pandoc-...@googlegr= oups.com> wrote:
> > I thank you for the suggestion. It is proving somewhat ha= rd to (dis)
> confirm. I have made a testfile with just the word "test&= quot; pasted over and
> over again, with and without various formatting and with the s= ame length or
> longer as the proper papers. This file consistently works. But= when I
> attempt to do it with a regular research paper, it only works = if I shorten
> it. Curiously, I can remove either half of the main text, or i= ndeed
> sections here and there, randomly, and it works, but not with = all of them
> present. I have combed it for special characters or tags, but = cannot find
> any.
> >
> > mandag 27. februar 2023 kl. 13:49:58 UTC+1 skrev Bernardo= C. D. A.
> Vasconcelos:
> > I do not know the answer to this problem in particular, b= ut perhaps it is
> worth checking the main document and the bibliography for invi= sible control
> characters (e.g. `\X{A0}`). They tend to cause all sorts of st= range
> problems that result in random error msgs.
> >
> > On Monday, February 27, 2023 at 8:16:20=E2=80=AFAM UTC-3 = Peter Vedal Utnes wrote:
> > We have a workflow in Open Journal Systems where we use P= andoc to convert
> word documents to EPUB, and then display them with an embedded= EPUB app
> (Bibi).
> >
> > Our resulting EPUBs work fine with both debuggers and vie= wers like
> calibre. They work in Bibi, but only when they are reduced to = a certain
> length. Whenever the files exceed approx 100 lines or 600 word= s, Bibi
> claims:
> >
> > TypeError: Cannot read properties of undefined (reading = =E2=80=98getAttribute=E2=80=99)
> >
> > Meanwhile, the same documents works when converted to EPU= B using other
> converters, or when I reduce the length (length, not size in b= ytes-- I've
> tried with graphics, still works). It suddenly works when I re= duce the
> length by removing pure paragraph text, even though all the fo= rmatted
> elements (abstract, references, etc) are the same.
> >
> > I recognize that this problem is very specific to the int= errelation
> pandoc <-> Bibi, but I'd be grateful for general tro= ubleshooting
> suggestions.
> >
> > Thanks in advance,
> >
> > Peter
> >
> >
> > --
> > You received this message because you are subscribed to a= topic in the
> Google Groups "pandoc-discuss" group.
> > To unsubscribe from this topic, visit [1]https://groups.google.com/d/
> topic/pandoc-discuss/hPUa1uWGS_k/unsubscribe.
> > To unsubscribe from this group and all its topics, send a= n email to=20
> pandoc-discus...@go= oglegroups.com.
> > To view this discussion on the web visit [2]https://groups.google.com/d/
> msgid/pandoc-discuss/
> 4bd152b5-32f7-4f4c-9a9b-0d20afebea84n%40googlegroups.com.
> >
> > --
> > You received this message because you are subscribed to t= he Google Groups
> "pandoc-discuss" group.
> > To unsubscribe from this group and stop receiving emails = from it, send an
> email to pandoc-dis= cus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
> > To view this discussion on the web visit [3]https://groups.google.com/d/
> msgid/pandoc-discuss/
> bc147d77-69c9-4e5d-82a6-e149f662a823n%40googlegroups.com.
>=20
>=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 email
> to [4]pandoc-discus...@= googlegroups.com.
> To view this discussion on the web visit [5]https://groups.google.com/d/msgid/
> pandoc-discuss/20942a45-0995-4a50-888a-cf25e9895920n%40googlegroups.com.
>=20
> References:
>=20
> [1] https://groups.= google.com/d/topic/pandoc-discuss/hPUa1uWGS_k/unsubscribe
> [2] https://groups.google.c= om/d/msgid/pandoc-discuss/4bd152b5-32f7-4f4c-9a9b-0d20afebea84n%40googlegro= ups.com
> [3] https://groups.google.c= om/d/msgid/pandoc-discuss/bc147d77-69c9-4e5d-82a6-e149f662a823n%40googlegro= ups.com
> [4] mailto:pandoc-discu= s...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [5] https://groups= .google.com/d/msgid/pandoc-discuss/20942a45-0995-4a50-888a-cf25e9895920n%40= googlegroups.com?utm_medium=3Demail&utm_source=3Dfooter

--
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/a484697f-9076-4a13-acf1-a645fa611614n%40googlegroups.= com.
------=_Part_4857_1618590406.1677516585685-- ------=_Part_4856_1011065552.1677516585685--