From: t t <tobias.tschiedl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: problem with urls in bibliography (pdf output)
Date: Tue, 31 Oct 2023 12:21:32 -0700 (PDT) [thread overview]
Message-ID: <b82b1b49-4c9d-4534-9b41-831bab0917c6n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1898 bytes --]
Hi,
I'm getting garbled URLs in the pdf output for a bibliography. I'm not sure
what I am doing wrong.
By garbled, I mean this here, copied from the pdf (note all the happy %20s):
Pitt, David. 2022. “Mental Representation.” In The Stanford Encyclopedia of
Philosophy, edited by Edward N. Zalta and Uri Nodelman, Fall 2022.
%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%
20%20%20%20https://plato.stanford.edu/archives/fall2022/entries/mentalrepresentation/%0A%20%20%20%20%20%20%20%20%20%20%20%20%
20%20%20%20%20%20%20%20; Metaphysics Research Lab, Stanford University.
Got this through calling `pandoc mwe.bib -s --citeproc -o mwe.pdf` like
suggested in a manual.
(I had similar results calling it as --bibliography, with the main input a
.tex file that included \usepackage{url}, so that does not seem to be the
problem)
The mwe.bib file that produced this is this:
```
@incollection{sep-mental-representation,
author = {Pitt, David},
booktitle = {The {Stanford} Encyclopedia of Philosophy},
edition = {{F}all 2022},
editor = {Edward N. Zalta and Uri Nodelman},
howpublished = {\url{
https://plato.stanford.edu/archives/fall2022/entries/mental-representation/
}},
publisher = {Metaphysics Research Lab, Stanford University},
title = {{Mental Representation}},
year = {2022},
}
```
Any ideas what I might have overlooked here?
Thanks,
Best,
Tobias
--
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/b82b1b49-4c9d-4534-9b41-831bab0917c6n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2364 bytes --]
next reply other threads:[~2023-10-31 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 19:21 t t [this message]
[not found] ` <b82b1b49-4c9d-4534-9b41-831bab0917c6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-10-31 20:14 ` John MacFarlane
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=b82b1b49-4c9d-4534-9b41-831bab0917c6n@googlegroups.com \
--to=tobias.tschiedl-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).