Re: [xml2rfc] Page break before large <artwork>/<sourcecode> element

Sandy Ginoza <sginoza@amsl.com> Fri, 02 April 2021 16:43 UTC

Return-Path: <sginoza@amsl.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 206233A1CB1 for <xml2rfc@ietfa.amsl.com>; Fri, 2 Apr 2021 09:43:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IsdMH53cKh9V for <xml2rfc@ietfa.amsl.com>; Fri, 2 Apr 2021 09:43:19 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3EE73A1CB0 for <xml2rfc@ietf.org>; Fri, 2 Apr 2021 09:43:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id B709B389EBD; Fri, 2 Apr 2021 09:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5BdN5MkV3RR8; Fri, 2 Apr 2021 09:43:18 -0700 (PDT)
Received: from 2603-8000-9603-b513-f104-0b2b-bb53-d1c0.res6.spectrum.com (2603-8000-9603-b513-f104-0b2b-bb53-d1c0.res6.spectrum.com [IPv6:2603:8000:9603:b513:f104:b2b:bb53:d1c0]) by c8a.amsl.com (Postfix) with ESMTPSA id 943313898BC; Fri, 2 Apr 2021 09:43:18 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Sandy Ginoza <sginoza@amsl.com>
In-Reply-To: <f754d0e0-7afe-522c-cc70-a69d7fd7e043@gmx.de>
Date: Fri, 2 Apr 2021 09:43:23 -0700
Cc: xml2rfc@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC6EC7E8-1F5B-4ABD-A575-01330EB707ED@amsl.com>
References: <005001d727aa$4a3f1250$debd36f0$@gwerder.net> <f754d0e0-7afe-522c-cc70-a69d7fd7e043@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/kkGi2kLZnYU1o0h1HFsesVqKrA8>
Subject: Re: [xml2rfc] Page break before large <artwork>/<sourcecode> element
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Apr 2021 16:43:24 -0000

Hi Martin,

You can try keepWithPrevious=“true” and/or keepWithPrevious=“true”, but it doesn’t always help.

Unfortunately, this is not uncommon in the PDFs.  https://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/463 details some page break issues.

Thanks,
Sandy 

> On Apr 2, 2021, at 7:22 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> Am 02.04.2021 um 12:23 schrieb Martin Gwerder:
>> Hi all
>> 
>> Is anyone aware of a way to suppress the page break before a large
>> artwork/sourcecode element when using the pdf renderer?
>> 
>> I do not think that it is a bug in principal but maybe something of the
>> category “not nice”. The renderer seems to work by the logic “if does
>> not fit on the current page then insert page break”. In my eyes it
>> should be “if not fit on the current page AND ELEMENT IS SMALLER THAN A
>> PAGE then insert page break”. In my eyes it should be considered as a
>> future improvement. At the moment I would be very happy with a attribute
>> that allows me to suppress the initial page break at the beginning of an
>> artwork/sourcecode or any comparable workaround. Anyone aware of such a
>> thing?
> 
> That sounds like an actual bug, and I would report it at
> <https://trac.tools.ietf.org/tools/xml2rfc/trac/newticket>.
> 
> Best regards, Julian
> 
> _______________________________________________
> xml2rfc mailing list
> xml2rfc@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc
>