From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Missing biblio
Date: Sun, 6 Aug 2017 22:08:21 -0700 [thread overview]
Message-ID: <20170807050821.GC81152@Johns-MacBook-Pro.local> (raw)
In-Reply-To: <08b2ce82-4d36-4e6b-be2c-b8fb0dddec97-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Try langid or hyphenation instead of (or in addition to) language.
See https://tex.stackexchange.com/questions/96469/switching-languages-in-bibliography-with-biblatex
+++ Robert Goulding [Aug 06 17 14:52 ]:
> Escaping the colon works perfectly, after testing.
> I had one other query. When I convert to docx, the foreign titles are
> put into sentence case, despite the fact that I have the language field
> set. So, for example, the entry in my bibtex file:
> @BOOK{Weinrich1998-zr,
> title = "Die Lichtbrechung in den Theorien von Descartes und
> Fermat",
> author = "Weinrich, Klaus",
> publisher = "F. Steiner",
> series = "Sudhoffs Archiv: Beihefte",
> year = 1998,
> address = "Stuttgart",
> language = "de"
> }
> turns up in my bibliography as: Weinrich, Klaus. 1998. Die
> Lichtbrechung in Den Theorien von Descartes Und Fermat. Sudhoffs
> Archiv: Beihefte. Stuttgart: F. Steiner.
>
> with "den" and "und" capitalized (but not "von"!). I see this behavior
> whether or notI explicitly include the Chicago csl file from the Zotero
> repository, or just use the pandoc default.
> Robert.
> On Sunday, August 6, 2017 at 5:33:36 PM UTC-4, Robert Goulding wrote:
>
> Thank you! I will backslash the colons in the file as a fix for now. -
> Robert.
> On Sunday, August 6, 2017 at 12:02:43 PM UTC-4, John MacFarlane wrote:
>
> Thanks (and apologies if I missed the files before).
> Simple repro here:
> ```
> hi[^fn3]
> [^fn3]: [@Alhazen1572-qk, V.9]: "competentius est et rationabilius,
> ut appareat supra perpendiculum, quam extra eam."
> ```
> This yields an empty footnote. Why? Because the footnote
> contains:
> ```
> [@Alhazen1572-qk, V.9]: "competentius est et rationabilius, ut
> appareat supra perpendiculum, quam extra eam."
> ```
> which pandoc is parsing as a reference link definition!
> Perhaps pandoc should not allow reference link definitions
> that start with `@`, since these conflict with citations?
> Anyone have thoughts about this? Someone should probably
> put an issue on the bug tracker for this.
> In the mean time, a workaround is to backslash-escape the
> colon:
> [@Alhazen1572-qk, V.9]\: "competentius...
>
> --
> 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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/08b2ce82-4d36-4e6b-
> be2c-b8fb0dddec97%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-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/08b2ce82-4d36-4e6b-be2c-b8fb0dddec97-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
next prev parent reply other threads:[~2017-08-07 5:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 19:59 Robert Goulding
[not found] ` <185cf47c-84e5-41b3-8a88-ba092bc4f191-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-05 17:06 ` John MacFarlane
2017-08-06 14:17 ` Robert Goulding
[not found] ` <b1e81aba-1be2-4b68-b76a-1147c0ca0472-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-06 14:18 ` Robert Goulding
[not found] ` <93a2e736-ac22-48d5-abe6-78e002859383-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-06 16:02 ` John MacFarlane
2017-08-06 21:33 ` Robert Goulding
[not found] ` <883d77fb-5e85-4b8a-8efe-96e629ff032a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-06 21:52 ` Robert Goulding
[not found] ` <08b2ce82-4d36-4e6b-be2c-b8fb0dddec97-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-07 5:08 ` John MacFarlane [this message]
[not found] ` <20170807050821.GC81152-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2017-08-10 13:45 ` Robert Goulding
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=20170807050821.GC81152@Johns-MacBook-Pro.local \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).