From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/17969 Path: news.gmane.org!.POSTED!not-for-mail From: Eric Driscoll Newsgroups: gmane.text.pandoc Subject: page breaking and \hypertarget again Date: Mon, 31 Jul 2017 16:43:22 -0700 (PDT) Message-ID: <2be4246c-1e31-4f7b-b931-3d552c63cb2d@googlegroups.com> Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_3864_1987937556.1501544602199" X-Trace: blaine.gmane.org 1501544612 7168 195.159.176.226 (31 Jul 2017 23:43:32 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 31 Jul 2017 23:43:32 +0000 (UTC) To: pandoc-discuss Original-X-From: pandoc-discuss+bncBC6YN762QUNBBGUB77FQKGQEHJJXYSI-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Tue Aug 01 01:43:26 2017 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane.org Original-Received: from mail-io0-f185.google.com ([209.85.223.185]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dcKLF-0001A8-GK for gtp-pandoc-discuss@m.gmane.org; Tue, 01 Aug 2017 01:43:17 +0200 Original-Received: by mail-io0-f185.google.com with SMTP id q64sf273641ioi.3 for ; Mon, 31 Jul 2017 16:43:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20161025; h=sender:date:from:to:message-id:subject:mime-version :x-original-sender:reply-to:precedence:mailing-list:list-id :list-post:list-help:list-archive:list-subscribe:list-unsubscribe; bh=GdDla9B0ZxHrAS/pf533vzb9eZXGey3JW0FjE6BGM3g=; b=Ha6ifNV8x2hGoBGrsWYQgGG8HvyPwqaw+4i73FI9ZQodgUUgeDgLYqqmJ/LSzLxMHM jnBFDDUC+HKzO/eOuUorqX8X9C8LvPuKPFfJwBCCyoqLZPlMytRyLbzM1fVjZ4L4xWOM Vau89PkfR64iuP3gw4oF+Y6tTj/jFFoYNfyC2YsjCbuZBpGBlTHMrhMSEo+0udC4FjW9 OwzfXXZFiEmrEnyKaPcF8Oomu31G3VcZbGS4o2ByGvjPIa3ky6LNTu6M0K0k79O9tBvD M1kVo/Rq7n8SOke3xwpVUqf6aevCO4b7+TgQ6ygdVwuUR8uykwl9VIN+k/X4hJ1XYhwg F+XQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:subject:mime-version:x-original-sender :reply-to:precedence:mailing-list:list-id:list-post:list-help :list-archive:list-subscribe:list-unsubscribe; bh=GdDla9B0ZxHrAS/pf533vzb9eZXGey3JW0FjE6BGM3g=; b=tLnyruED9F3Bw78AwF5XcTSoTp2Y2juRnKnavyZYseTj6CaXB2iFjiIjEq8GTXqkyK qnOfY5be5uM19RsWY8Z1QbQAucw4U9XOSX4rNmpIUkKeK+kmx3vVoRdfVlUte30OseEm vXhPYVLTBimXxeMzVAOHXOrTPirN73wxsJXFPQbVqWzLcXCvlgVDkePE6TWAtufV7xV1 JNnQQmmmtKZt5VjKtx7AyDFSKiaDVdqMjgFYxbu6ezd1gRSRc7AfEU86f9khEZ4yYDtU 0suL+AaldEV3Ry9h+IG8tWjUwCt4hN3Ecsw8GcWSpT/BBtPR8gtEruEeIhvdcI2S8Qqy T+FA== 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: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=GdDla9B0ZxHrAS/pf533vzb9eZXGey3JW0FjE6BGM3g=; b=t0yS9OIgenX8KJROZ320Lp0oymZ+WUK9xsq1E8syplJi0KCSosDoEI1YBtkvbjAUCM lCOUJ6Gh45hWciAH7uuTVF3RgALfxTaTXnLwgxjhwosMTadeG8lk7WKiTS6K33VlkrSM watJnKdbgP6ZiZCaXjl/dqk0jO+UhS0IzHYiZh7zcyZ3LXyMIWFxtyEOGpZC84ITfvqh +6ShlWGOO6YyjsQgi4olcksj+NcvFWiyk8PfJ6gR8TU+8BKgXJvs0hcHZRhoystJN8Mk gSmOKz2DEcz8wxYsLAPzUtbWPRffI5rALfq7sOomw5z0CGZ3119+ddtsgNyPuumyFp8H lQNg== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: AIVw111qT/yG/UDdeqduoxFwkVFIah474neXfOTL3+bR0wsuDLseA4pQ 6BIAbokccvFb3Q== X-Received: by 10.36.79.146 with SMTP id c140mr680449itb.11.1501544603421; Mon, 31 Jul 2017 16:43:23 -0700 (PDT) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 10.36.138.65 with SMTP id v62ls17465itd.3.canary-gmail; Mon, 31 Jul 2017 16:43:22 -0700 (PDT) X-Received: by 10.36.39.140 with SMTP id g134mr113ita.7.1501544602665; Mon, 31 Jul 2017 16:43:22 -0700 (PDT) X-Original-Sender: palinurus-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:17969 Archived-At: ------=_Part_3864_1987937556.1501544602199 Content-Type: multipart/alternative; boundary="----=_Part_3865_340220814.1501544602200" ------=_Part_3865_340220814.1501544602200 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable An issue discussed briefly earlier on this forum=20 (https://groups.google.com/d/topic/pandoc-discuss/IR7nL7lEHpc/discussion)= =20 still seems to exist and seems to require a solution at the pandoc-citeproc= =20 level.=20 Essentially, the problem is that the \hypertarget{ref-soandso} inserted in= =20 front of entries in the bibliography has the counterintuitive and obviously= =20 undesirable side effect of preventing page breaks between entries--only=20 within them. That is, if you have a reference occupying two lines in the=20 bibliography followed by half a page of single-line items and then another= =20 multi-line entry, the resulting PDF will have a page break between the two= =20 lines of the first entry followed by simple whitespace for the rest of the= =20 page. In other words, it's an absolute refusal to allow the page break to= =20 come between "paragraphs" in the bibliography, no matter how much=20 whitespace gets left behind as a result--obviously a ridiculous result. I'm sure there's a workaround. The solution offered in the discussion=20 linked above was to place this just before the bibliography:=20 \let\oldhypertarget\hypertarget \renewcommand{\hypertarget}[2]{% \leavevmode% \oldhypertarget{#1}{#2}% }
Doing so, however, in turn has the unexpected effect of messing with the=20 left alignment of some references--many are still where they should be,=20 while others are indented random amounts. So that's not great either. I'm= =20 not sure why \leavevmode is having this effect, if it is, but, again, not= =20 acceptable.=20 Anyone have a solution to this problem? I'd hesitate to call it a bug, but= =20 it is certainly not how things should be.=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 e= mail 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. ------=_Part_3865_340220814.1501544602200 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
An issue discussed briefly earlier on this forum (htt= ps://groups.google.com/d/topic/pandoc-discuss/IR7nL7lEHpc/discussion) still= seems to exist and seems to require a solution at the pandoc-citeproc leve= l.=C2=A0

Essentially, the problem is that the \hyp= ertarget{ref-soandso} inserted in front of entries in the bibliography has = the counterintuitive and obviously undesirable side effect of preventing pa= ge breaks between entries--only within them. That is, if you have a referen= ce occupying two lines in the bibliography followed by half a page of singl= e-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 w= hitespace for the rest of the page. In other words, it's an absolute re= fusal 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 th= ere's a workaround. The solution offered in the discussion linked above= was to place this just before the bibliography:=C2=A0

=
\let\oldhypertarget\hypertarget

\renewcommand= {\hypertarget}[2]{%
=C2=A0 =C2=A0 \leavevmode%
=C2=A0 = =C2=A0 \oldhypertarget{#1}{#2}%
}

<di= v id=3D=E2=80=9Crefs=E2=80=9D></div>

Doin= g so, however, in turn has the unexpected effect of messing with the left a= lignment of some references--many are still where they should be, while oth= ers are indented random amounts. So that's not great either. I'm no= t sure why \leavevmode is having this effect, if it is, but, again, not acc= eptable.=C2=A0

Anyone have a solution to this prob= lem? I'd hesitate to call it a bug, but it is certainly not how things = should be.=C2=A0

--
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/2be4246c-1e31-4f7b-b931-3d552c63cb2d%40googlegroups.co= m.
For more options, visit http= s://groups.google.com/d/optout.
------=_Part_3865_340220814.1501544602200-- ------=_Part_3864_1987937556.1501544602199--