From: Eric Driscoll <palinurus-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: page breaking and \hypertarget again
Date: Mon, 31 Jul 2017 16:43:22 -0700 (PDT) [thread overview]
Message-ID: <2be4246c-1e31-4f7b-b931-3d552c63cb2d@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2275 bytes --]
An issue discussed briefly earlier on this forum
(https://groups.google.com/d/topic/pandoc-discuss/IR7nL7lEHpc/discussion)
still seems to exist and seems to require a solution at the pandoc-citeproc
level.
Essentially, the problem is that the \hypertarget{ref-soandso} inserted in
front of entries in the bibliography has the counterintuitive and obviously
undesirable side effect of preventing page breaks between entries--only
within them. That is, if you have a reference occupying two lines in the
bibliography followed by half a page of single-line items and then another
multi-line entry, the resulting PDF will have a page break between the two
lines of the first entry followed by simple whitespace for the rest of the
page. In other words, it's an absolute refusal to allow the page break to
come between "paragraphs" in the bibliography, no matter how much
whitespace gets left behind as a result--obviously a ridiculous result.
I'm sure there's a workaround. The solution offered in the discussion
linked above was to place this just before the bibliography:
\let\oldhypertarget\hypertarget
\renewcommand{\hypertarget}[2]{%
\leavevmode%
\oldhypertarget{#1}{#2}%
}
<div id=“refs”></div>
Doing so, however, in turn has the unexpected effect of messing with the
left alignment of some references--many are still where they should be,
while others are indented random amounts. So that's not great either. I'm
not sure why \leavevmode is having this effect, if it is, but, again, not
acceptable.
Anyone have a solution to this problem? I'd hesitate to call it a bug, but
it is certainly not how things should be.
--
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/2be4246c-1e31-4f7b-b931-3d552c63cb2d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2908 bytes --]
reply other threads:[~2017-07-31 23:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2be4246c-1e31-4f7b-b931-3d552c63cb2d@googlegroups.com \
--to=palinurus-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).