From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/18575 Path: news.gmane.org!.POSTED!not-for-mail From: Denis Maier Newsgroups: gmane.text.pandoc Subject: Re: Ibid. ambiguity Date: Thu, 9 Nov 2017 01:05:37 -0800 (PST) Message-ID: <2e01906a-5449-44cc-834c-3e87ef3c30a2@googlegroups.com> References: <5f1ba639-7d7c-49e1-b48f-5f7cba72f1dd@googlegroups.com> <20140902174840.GA95334@dhcp-128-32-252-25.lips.berkeley.edu> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_4313_243037073.1510218338006" X-Trace: blaine.gmane.org 1510218344 18750 195.159.176.226 (9 Nov 2017 09:05:44 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 9 Nov 2017 09:05:44 +0000 (UTC) To: pandoc-discuss Original-X-From: pandoc-discuss+bncBCQOJL5Q2QMRBY5USDIAKGQEAWYIRMQ-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Thu Nov 09 10:05:35 2017 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane.org Original-Received: from mail-oi0-f58.google.com ([209.85.218.58]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eCimC-0004TJ-U6 for gtp-pandoc-discuss@m.gmane.org; Thu, 09 Nov 2017 10:05:33 +0100 Original-Received: by mail-oi0-f58.google.com with SMTP id 14sf4118038oii.2 for ; Thu, 09 Nov 2017 01:05:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20161025; 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=CjBoDLAhqeY4czfj2GHo/rWeaw/X3fHwpULzRxiZ3Jk=; b=bHrYQgWHaXYLs82eN8yN0ckAtJqZmgVqn1+I+VyV7LiG9CaaocfQr9skQK3EMmUNUZ S87aHBNXiunwb6ht17J6Nzffo0s33VTM+PzM3WYQLb+dobNQ0hZ0kGogA8hmbE+s9fIv Zt5jhUuznH3aWEacnu7A79dI/fHGBHEpUMR+xUHvEewIhgy6Oa0ThvierbgC6gW4TL6Y nUbO2tGDJOl/J776/abO+tfQhrB/nLNy/46Kb+UifPzAwV0gF900WSUjUxLypYTDmFON K0MwExZBQOkVWk1fBazuuzF0AJOAMnat9Ff4f9FfBv9GrFTYFzzv8yvbirx16Ctx5q0A AHdQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; 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=CjBoDLAhqeY4czfj2GHo/rWeaw/X3fHwpULzRxiZ3Jk=; b=N6K+QPTOhrSNlIKd2tXN9s08fmnaPBRXercKfHeAp6yxOuurz0hMRpsXiCsjKW8Z29 ASfGXVdJskiUDFMqm4NNsX6Afsc7ULD/+xzj1lnHfpm+2mbHDvOWvMypfIBWrPsXeXdK qBkqZw+U7CVhqOkuNaKGijcHaeUhMp9lZwj6dPB7xcdLIgrJt4ZP9Z9jUPraDP1c3XmS i6eYXYrdTirLVpgHJ8RwokIaq+mrNlrxjYGPysVy44iYp+uAlf8yf5jsG+WDUDaXs8jr 16bkldhYh0UValPa+9OYD2KZUdsKrDEqIanl+T3KvLBDnDe74t8Odu3sdOkv5K7ZjUHu BynQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; 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=CjBoDLAhqeY4czfj2GHo/rWeaw/X3fHwpULzRxiZ3Jk=; b=D4Wv6jT/XeadtOTZmUSyh0j/lIKFtjULBIzhKZ/QSIkYr/4rBN9FdeAiJ0oTC0hEaS fi12lqK063/fdr4Bv+Zu2dcF54u7cKyko4M3/FHlD1l2XD6hbOlfwkRvgwmjtUbQuJBv idwdEr5LxWh57pX6WVdpuhQSf4NAoWMuUBwivW/ElrVYflIKyh27/S55phG3V4wfHGeM rC/ZNH8Zw67tl1WjSLHt9xQ7c03bEb+lL9e9C/nK0axKyx/LFJAcZ9Tyw8/au3Qni3ef Ls3YdApLTyh0/gyNQjNUoiMU7xcGjTBalopM+drPZTWVI9kO1Rb5VyJp+eVF7kEMzRLq pBLA== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: AJaThX5XWTKmBJXxkzwDqKms5BBrmmTBSxaf2269CsMv+rhvydwvWWaR 1MIWC/JiVD6MzpE3wcf3xMg= X-Google-Smtp-Source: AGs4zMYLdObF9hm0txTHkP9l3hPKRQqZ2y7KPKot5Bv4z/NpK/REGNOT0mJpFBndmYFqV+mgNLA5ag== X-Received: by 10.157.94.7 with SMTP id d7mr205188oti.8.1510218340308; Thu, 09 Nov 2017 01:05:40 -0800 (PST) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 10.202.4.208 with SMTP id 199ls5411799oie.7.gmail; Thu, 09 Nov 2017 01:05:39 -0800 (PST) X-Received: by 10.157.40.232 with SMTP id s95mr201605ota.12.1510218338484; Thu, 09 Nov 2017 01:05:38 -0800 (PST) In-Reply-To: <20140902174840.GA95334-0VdLhd/A9Pm0ooXD8Eul3cvGpKv5k03bTVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> X-Original-Sender: maier.de-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.org gmane.text.pandoc:18575 Archived-At: ------=_Part_4313_243037073.1510218338006 Content-Type: multipart/alternative; boundary="----=_Part_4314_1552287536.1510218338007" ------=_Part_4314_1552287536.1510218338007 Content-Type: text/plain; charset="UTF-8" Are there any news on this? I have found a solution that works quite ok. I use a fake reference that I cite between two real references. ~~~~~~~~~~~~~~~~~~~~~ --- references: - id: a title: test author: - family: familyname given: givenname type: article-journal issued: year: 2014 - id: mancite title: !mancite! ... Sentence 1. [@a] Sentence 2.^[Some text in a footnote. @mancite] Sentence 3. [@a] ~~~~~~~~~~~~~~~~~~~~~ Then I use the following workflow: 1. Run pandoc on this file, create a new markdown file with resolved citations. 2. Use sed to get rid of the mancite-citations and the mancite-reference-entry in the bilbiography. 3. Run pandoc on this final file to create a pdf, docx, etc. This works, but it is not elegant. One problem is that the sed replacement rules only apply to a given citation style. Does anyone know a better solution? Perhaps a pandoc filter so that I don't need sed to clean up the file (one tool less involved)? And, is there a way to suppress certain entries in the bibliography? Am Dienstag, 2. September 2014 19:48:49 UTC+2 schrieb John MacFarlane: > > Thanks for the bug report on github, which I saw. I will try to > fix this when I can, but probably not in the very near future. > I am still trying to get on top of some of the old citeproc-hs > code. There are still quite a few problems with disambiguation > in footnote styles, and this is related. It will be solved in time. > > +++ Denis Maier [Sep 02 14 08:07 ]: > > Hey there, > > I have recently posted a problem on github concerning pandoc-citeproc > > (https://github.com/jgm/pandoc-citeproc/issues/79) and I am just > > wondering if anybody else has run into that kind of problems, or if > > anyone has an idea how this can be solved. > > The problem is that when using a citation style that supports "Ibid." > > (I am using "chicago-fullnote-bibliography") pandoc-citeproc produces > > ambiguous or wrong results. Consider this example: > > ~~~~~~~~~~~~~~~~~~~~~ > > --- > > references: > > - id: a > > title: test > > author: > > - family: familyname > > given: givenname > > type: article-journal > > issued: > > year: 2014 > > ... > > Sentence 1. [@a] > > Sentence 2.^[Many examples can be found in the Babylonian Talmud.] > > Sentence 3. [@a] > > ~~~~~~~~~~~~~~~~~~~~~ > > After Sentence 3 the source is rendered as "Ibid.". It should print > the > > normal citation instead since after sentence 2 we have another > > footnote. (A similar example in LibreOffice with Zotero works just > > fine. Is it possible that pandoc-citeproc does not take "near-note" > > into account?) > > The same also applies for author-date styles that use "Ibid." if we > > enter a manual citation from a classical source like the bible between > > two identical sources: > > ~~~~~~~~~~~~~~~~~~~~~ > > --- > > references: > > - id: a > > title: test > > author: > > - family: familyname > > given: givenname > > type: article-journal > > issued: > > year: 2014 > > ... > > Sentence [@a]. Sentence (see Exodus 1:1). Sentence 3 [@a]. > > ~~~~~~~~~~~~~~~~~~~~~ > > ==> Sentence (familyname, test). Sentence (see Exodus 1:1). Sentence 3 > > (ibid.). > > Looking at this more generally, the problem is that certain sources > can > > not easily be rendered automatically. The rules for citing classical > > sources (like the bible, the talmud, the quran, other religious texts, > > texts from Greek and Roman antiquity) are often obscure, and can > hardly > > be automated. So it is often more convenient to enter the reference > > manually. But this conflicts of course with automatically generated > > references. > > In BibLaTeX there is a command "\mancite" that prevents the wrong > > "ibid.". Perhaps it might be feasible to implement something like this > > in pandoc-citeproc? If I am converting to LaTeX I could of course > enter > > \mancite as a raw tex command. However, I'd prefer to be as > independent > > of any particular output format as possible so suggestions that work > > also when going from markdown to odt or docx are highly appreciated. > > Best, > > Denis > > > > -- > > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To post to this group, send email to > > [2]pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To view this discussion on the web visit > > [3] > https://groups.google.com/d/msgid/pandoc-discuss/5f1ba639-7d7c-49e1- > > b48f-5f7cba72f1dd%40googlegroups.com. > > For more options, visit [4]https://groups.google.com/d/optout. > > > >References > > > > 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > > 2. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > > 3. > https://groups.google.com/d/msgid/pandoc-discuss/5f1ba639-7d7c-49e1-b48f-5f7cba72f1dd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer > > > 4. https://groups.google.com/d/optout Am Dienstag, 2. September 2014 19:48:49 UTC+2 schrieb John MacFarlane: > > Thanks for the bug report on github, which I saw. I will try to > fix this when I can, but probably not in the very near future. > I am still trying to get on top of some of the old citeproc-hs > code. There are still quite a few problems with disambiguation > in footnote styles, and this is related. It will be solved in time. > > +++ Denis Maier [Sep 02 14 08:07 ]: > > Hey there, > > I have recently posted a problem on github concerning pandoc-citeproc > > (https://github.com/jgm/pandoc-citeproc/issues/79) and I am just > > wondering if anybody else has run into that kind of problems, or if > > anyone has an idea how this can be solved. > > The problem is that when using a citation style that supports "Ibid." > > (I am using "chicago-fullnote-bibliography") pandoc-citeproc produces > > ambiguous or wrong results. Consider this example: > > ~~~~~~~~~~~~~~~~~~~~~ > > --- > > references: > > - id: a > > title: test > > author: > > - family: familyname > > given: givenname > > type: article-journal > > issued: > > year: 2014 > > ... > > Sentence 1. [@a] > > Sentence 2.^[Many examples can be found in the Babylonian Talmud.] > > Sentence 3. [@a] > > ~~~~~~~~~~~~~~~~~~~~~ > > After Sentence 3 the source is rendered as "Ibid.". It should print > the > > normal citation instead since after sentence 2 we have another > > footnote. (A similar example in LibreOffice with Zotero works just > > fine. Is it possible that pandoc-citeproc does not take "near-note" > > into account?) > > The same also applies for author-date styles that use "Ibid." if we > > enter a manual citation from a classical source like the bible between > > two identical sources: > > ~~~~~~~~~~~~~~~~~~~~~ > > --- > > references: > > - id: a > > title: test > > author: > > - family: familyname > > given: givenname > > type: article-journal > > issued: > > year: 2014 > > ... > > Sentence [@a]. Sentence (see Exodus 1:1). Sentence 3 [@a]. > > ~~~~~~~~~~~~~~~~~~~~~ > > ==> Sentence (familyname, test). Sentence (see Exodus 1:1). Sentence 3 > > (ibid.). > > Looking at this more generally, the problem is that certain sources > can > > not easily be rendered automatically. The rules for citing classical > > sources (like the bible, the talmud, the quran, other religious texts, > > texts from Greek and Roman antiquity) are often obscure, and can > hardly > > be automated. So it is often more convenient to enter the reference > > manually. But this conflicts of course with automatically generated > > references. > > In BibLaTeX there is a command "\mancite" that prevents the wrong > > "ibid.". Perhaps it might be feasible to implement something like this > > in pandoc-citeproc? If I am converting to LaTeX I could of course > enter > > \mancite as a raw tex command. However, I'd prefer to be as > independent > > of any particular output format as possible so suggestions that work > > also when going from markdown to odt or docx are highly appreciated. > > Best, > > Denis > > > > -- > > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org . > > To post to this group, send email to > > [2]pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org . > > To view this discussion on the web visit > > [3] > https://groups.google.com/d/msgid/pandoc-discuss/5f1ba639-7d7c-49e1- > > b48f-5f7cba72f1dd%40googlegroups.com. > > For more options, visit [4]https://groups.google.com/d/optout. > > > >References > > > > 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > > 2. mailto:pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > > 3. > https://groups.google.com/d/msgid/pandoc-discuss/5f1ba639-7d7c-49e1-b48f-5f7cba72f1dd-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer > > 4. https://groups.google.com/d/optout > -- 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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/2e01906a-5449-44cc-834c-3e87ef3c30a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. ------=_Part_4314_1552287536.1510218338007 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Are there any news on this?

I have foun= d a solution that works quite ok. I use a fake reference that I cite betwee= n two real references.

~~~~~= ~~~~~~~~~~~~~~~~
---
references:
- id: a<= /div>
=C2=A0 title: test
=C2=A0 author:
=C2=A0 - family: fa= milyname
=C2=A0 =C2=A0 given: givenname
=C2=A0 type: article-journal
<= div>=C2=A0 issued:
=C2= =A0 =C2=A0 =C2=A0year: 2014
- id: ma= ncite
=C2=A0 title: !mancite!
...

Sentence 1. [@a]
Sentence 2.^[Some text in a footnote. @mancite]
Sentence 3. [@a]
~~~~~~~~~~= ~~~~~~~~~~~

Then I use the following = workflow:
1. Run pandoc on this file, create a new markdown file = with resolved citations.
2. Use sed to get rid of the mancite-cit= ations and the mancite-reference-entry in the bilbiography.
3. Ru= n pandoc on this final file to create a pdf, docx, etc.

This works, but it is not elegant. One problem is that the sed replac= ement rules only apply to a given citation style.

= Does anyone know a better solution? Perhaps a pandoc filter so that I don&#= 39;t need sed to clean up the file (one tool less involved)?=C2=A0

And, is there a way to suppress certain entries in the bib= liography?


Am Dienstag, 2. September 2014 19:4= 8:49 UTC+2 schrieb John MacFarlane:
Thanks for the bug report on github, which I saw. =C2=A0= I will try to=C2=A0
fix this when I can, but probably not in the very ne= ar future.=C2=A0
I am still trying to get on top of some of the old cite= proc-hs=C2=A0
code. =C2=A0There are still quite a few problems with disa= mbiguation=C2=A0
in footnote styles, and this is related. =C2=A0It will = be solved in time.=C2=A0

+++ Denis Maier [Sep 02 14 08:07 ]:=C2=A0> =C2=A0 Hey there,=C2=A0
> =C2=A0 I have recently posted a prob= lem on github concerning pandoc-citeproc=C2=A0
> =C2=A0 (https://github.com/jgm/pandoc-citeproc/issues/79) and I a= m just=C2=A0
> =C2=A0 wondering if anybody else has run into that kin= d of problems, or if=C2=A0
> =C2=A0 anyone has an idea how this can b= e solved.=C2=A0
> =C2=A0 The problem is that when using a citation st= yle that supports "Ibid."=C2=A0
> =C2=A0 (I am using "= chicago-fullnote-bibliography") pandoc-citeproc produces=C2=A0> =C2=A0 ambiguous or wrong results. Consider this example:=C2=A0
&g= t; =C2=A0 ~~~~~~~~~~~~~~~~~~~~~=C2=A0
> =C2=A0 ---=C2=A0
> =C2= =A0 references:=C2=A0
> =C2=A0 - id: a=C2=A0
> =C2=A0 =C2=A0 ti= tle: test=C2=A0
> =C2=A0 =C2=A0 author:=C2=A0
> =C2=A0 =C2=A0 -= family: familyname=C2=A0
> =C2=A0 =C2=A0 =C2=A0 given: givenname=C2= =A0
> =C2=A0 =C2=A0 type: article-journal=C2=A0
> =C2=A0 =C2=A0= issued:=C2=A0
> =C2=A0 =C2=A0 =C2=A0 =C2=A0year: 2014=C2=A0
> = =C2=A0 ...=C2=A0
> =C2=A0 Sentence 1. [@a]=C2=A0
> =C2=A0 Sente= nce 2.^[Many examples can be found in the Babylonian Talmud.]=C2=A0
>= =C2=A0 Sentence 3. [@a]=C2=A0
> =C2=A0 ~~~~~~~~~~~~~~~~~~~~~=C2=A0> =C2=A0 After Sentence 3 the source is rendered as "Ibid.".= It should print the=C2=A0
> =C2=A0 normal citation instead since aft= er sentence 2 we have another=C2=A0
> =C2=A0 footnote. (A similar exa= mple in LibreOffice with Zotero works just=C2=A0
> =C2=A0 fine. Is it= possible that pandoc-citeproc does not take "near-note"=C2=A0> =C2=A0 into account?)=C2=A0
> =C2=A0 The same also applies for = author-date styles that use "Ibid." if we=C2=A0
> =C2=A0 en= ter a manual citation from a classical source like the bible between=C2=A0<= br>> =C2=A0 two identical sources:=C2=A0
> =C2=A0 ~~~~~~~~~~~~~~~~= ~~~~~=C2=A0
> =C2=A0 ---=C2=A0
> =C2=A0 references:=C2=A0
&g= t; =C2=A0 - id: a=C2=A0
> =C2=A0 =C2=A0 title: test=C2=A0
> =C2= =A0 =C2=A0 author:=C2=A0
> =C2=A0 =C2=A0 - family: familyname=C2=A0> =C2=A0 =C2=A0 =C2=A0 given: givenname=C2=A0
> =C2=A0 =C2=A0 ty= pe: article-journal=C2=A0
> =C2=A0 =C2=A0 issued:=C2=A0
> =C2= =A0 =C2=A0 =C2=A0 =C2=A0year: 2014=C2=A0
> =C2=A0 ...=C2=A0
> = =C2=A0 Sentence [@a]. Sentence (see Exodus 1:1). Sentence 3 [@a].=C2=A0
= > =C2=A0 ~~~~~~~~~~~~~~~~~~~~~=C2=A0
> =C2=A0 =3D=3D> Sentence = (familyname, test). Sentence (see Exodus 1:1). Sentence 3=C2=A0
> =C2= =A0 (ibid.).=C2=A0
> =C2=A0 Looking at this more generally, the probl= em is that certain sources can=C2=A0
> =C2=A0 not easily be rendered = automatically. The rules for citing classical=C2=A0
> =C2=A0 sources = (like the bible, the talmud, the quran, other religious texts,=C2=A0
>= ; =C2=A0 texts from Greek and Roman antiquity) are often obscure, and can h= ardly=C2=A0
> =C2=A0 be automated. So it is often more convenient to = enter the reference=C2=A0
> =C2=A0 manually. But this conflicts of co= urse with automatically generated=C2=A0
> =C2=A0 references.=C2=A0> =C2=A0 In BibLaTeX there is a command "\mancite" that preve= nts the wrong=C2=A0
> =C2=A0 "ibid.". Perhaps it might be f= easible to implement something like this=C2=A0
> =C2=A0 in pandoc-cit= eproc? If I am converting to LaTeX I could of course enter=C2=A0
> = =C2=A0 \mancite as a raw tex command. However, I'd prefer to be as inde= pendent=C2=A0
> =C2=A0 of any particular output format as possible so= suggestions that work=C2=A0
> =C2=A0 also when going from markdown t= o odt or docx are highly appreciated.=C2=A0
> =C2=A0 Best,=C2=A0
&= gt; =C2=A0 Denis=C2=A0
>=C2=A0
> =C2=A0 --=C2=A0
> =C2=A0= You received this message because you are subscribed to the Google=C2=A0> =C2=A0 Groups "pandoc-discuss" group.=C2=A0
> =C2=A0= To unsubscribe from this group and stop receiving emails from it, send=C2= =A0
> =C2=A0 an email to [1]pan= doc-discus...@googlegroups.com.=C2=A0
> =C2=A0 To post to th= is group, send email to=C2=A0
> =C2=A0 [2]pandoc-...@googlegroups.com.=C2=A0
> =C2=A0 To vi= ew this discussion on the web visit=C2=A0
> =C2=A0 [3]https://groups.google.com/d/msgid/pandoc-dis= cuss/5f1ba639-7d7c-49e1-=C2=A0
> =C2=A0 b48f-5f7cba72f1dd%40g= ooglegroups.com.=C2=A0
> =C2=A0 For more options, visit [4]<= a href=3D"https://groups.google.com/d/optout" target=3D"_blank" rel=3D"nofo= llow">https://groups.google.com/d/optout.=C2=A0
>=C2=A0
&= gt;References=C2=A0
>=C2=A0
> =C2=A0 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org= =C2=A0
> =C2=A0 2. mailto:pand= oc-...@googlegroups.com=C2=A0
> =C2=A0 3.=C2=A0https://groups.google.com/d/msgid/pandoc= -discuss/5f1ba639-7d7c-49e1-b48f-5f7cba72f1dd@googlegroups.com?ut= m_medium=3Demail&utm_source=3Dfooter=C2=A0
> =C2=A0 4.= =C2=A0https://groups.google.com/d/optout=C2=A0

Am Dienstag, 2. September 2014 19:48:49 UTC+2 schrieb John MacFa= rlane:
Thanks for the bug repor= t on github, which I saw. =C2=A0I will try to
fix this when I can, but probably not in the very near future.
I am still trying to get on top of some of the old citeproc-hs
code. =C2=A0There are still quite a few problems with disambiguation
in footnote styles, and this is related. =C2=A0It will be solved in tim= e.

+++ Denis Maier [Sep 02 14 08:07 ]:
> =C2=A0 Hey there,
> =C2=A0 I have recently posted a problem on github concerning pando= c-citeproc
> =C2=A0 (https://github.com/jgm/pandoc-citeproc/issues/79) an= d I am just
> =C2=A0 wondering if anybody else has run into that kind of problem= s, or if
> =C2=A0 anyone has an idea how this can be solved.
> =C2=A0 The problem is that when using a citation style that suppor= ts "Ibid."
> =C2=A0 (I am using "chicago-fullnote-bibliography")= pandoc-citeproc produces
> =C2=A0 ambiguous or wrong results. Consider this example:
> =C2=A0 ~~~~~~~~~~~~~~~~~~~~~
> =C2=A0 ---
> =C2=A0 references:
> =C2=A0 - id: a
> =C2=A0 =C2=A0 title: test
> =C2=A0 =C2=A0 author:
> =C2=A0 =C2=A0 - family: familyname
> =C2=A0 =C2=A0 =C2=A0 given: givenname
> =C2=A0 =C2=A0 type: article-journal
> =C2=A0 =C2=A0 issued:
> =C2=A0 =C2=A0 =C2=A0 =C2=A0year: 2014
> =C2=A0 ...
> =C2=A0 Sentence 1. [@a]
> =C2=A0 Sentence 2.^[Many examples can be found in the Babylonian T= almud.]
> =C2=A0 Sentence 3. [@a]
> =C2=A0 ~~~~~~~~~~~~~~~~~~~~~
> =C2=A0 After Sentence 3 the source is rendered as "Ibid."= ;. It should print the
> =C2=A0 normal citation instead since after sentence 2 we have anot= her
> =C2=A0 footnote. (A similar example in LibreOffice with Zotero wor= ks just
> =C2=A0 fine. Is it possible that pandoc-citeproc does not take &qu= ot;near-note"
> =C2=A0 into account?)
> =C2=A0 The same also applies for author-date styles that use "= ;Ibid." if we
> =C2=A0 enter a manual citation from a classical source like the bi= ble between
> =C2=A0 two identical sources:
> =C2=A0 ~~~~~~~~~~~~~~~~~~~~~
> =C2=A0 ---
> =C2=A0 references:
> =C2=A0 - id: a
> =C2=A0 =C2=A0 title: test
> =C2=A0 =C2=A0 author:
> =C2=A0 =C2=A0 - family: familyname
> =C2=A0 =C2=A0 =C2=A0 given: givenname
> =C2=A0 =C2=A0 type: article-journal
> =C2=A0 =C2=A0 issued:
> =C2=A0 =C2=A0 =C2=A0 =C2=A0year: 2014
> =C2=A0 ...
> =C2=A0 Sentence [@a]. Sentence (see Exodus 1:1). Sentence 3 [@a].
> =C2=A0 ~~~~~~~~~~~~~~~~~~~~~
> =C2=A0 =3D=3D> Sentence (familyname, test). Sentence (see Exodu= s 1:1). Sentence 3
> =C2=A0 (ibid.).
> =C2=A0 Looking at this more generally, the problem is that certain= sources can
> =C2=A0 not easily be rendered automatically. The rules for citing = classical
> =C2=A0 sources (like the bible, the talmud, the quran, other relig= ious texts,
> =C2=A0 texts from Greek and Roman antiquity) are often obscure, an= d can hardly
> =C2=A0 be automated. So it is often more convenient to enter the r= eference
> =C2=A0 manually. But this conflicts of course with automatically g= enerated
> =C2=A0 references.
> =C2=A0 In BibLaTeX there is a command "\mancite" that pr= events the wrong
> =C2=A0 "ibid.". Perhaps it might be feasible to implemen= t something like this
> =C2=A0 in pandoc-citeproc? If I am converting to LaTeX I could of = course enter
> =C2=A0 \mancite as a raw tex command. However, I'd prefer to b= e as independent
> =C2=A0 of any particular output format as possible so suggestions = that work
> =C2=A0 also when going from markdown to odt or docx are highly app= reciated.
> =C2=A0 Best,
> =C2=A0 Denis
>
> =C2=A0 --
> =C2=A0 You received this message because you are subscribed to the= Google
> =C2=A0 Groups "pandoc-discuss" group.
> =C2=A0 To unsubscribe from this group and stop receiving emails fr= om it, send
> =C2=A0 an email to [1]pandoc-discus...@googlegroups.com.
> =C2=A0 To post to this group, send email to
> =C2=A0 [2]pandoc-...@googlegroups.com.
> =C2=A0 To view this discussion on the web visit
> =C2=A0 [3]http= s://groups.google.com/d/msgid/pandoc-discuss/5f1ba639-7d7c-49e1-<= /a>
> =C2=A0 b48f-5f7cba72f1dd%40googlegroups.com.
> =C2=A0 For more options, visit [4]https:= //groups.google.com/d/optout.
>
>References
>
> =C2=A0 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> =C2=A0 2. mailto:pandoc-...@googlegroups.com
> =C2=A0 3. https://groups.google.com/d/msgid/pandoc-discuss/5f1ba639-7= d7c-49e1-b48f-5f7cba72f1dd@googlegroups.com?utm_medium=3Demail&am= p;utm_source=3Dfooter
> =C2=A0 4. https://groups.google.com/d/optout

--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To view this discussion on the web visit https://groups.google.com/d/= msgid/pandoc-discuss/2e01906a-5449-44cc-834c-3e87ef3c30a2%40googlegroups.co= m.
For more options, visit http= s://groups.google.com/d/optout.
------=_Part_4314_1552287536.1510218338007-- ------=_Part_4313_243037073.1510218338006--