From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id iBZrN1EGNGUASgAA9RJhRA:P1 (envelope-from ) for ; Sat, 21 Oct 2023 19:11:46 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id iBZrN1EGNGUASgAA9RJhRA (envelope-from ) for ; Sat, 21 Oct 2023 19:11:45 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 95CD440BCB for ; Sat, 21 Oct 2023 19:11:45 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=guelker.eu header.s=MBO0001 header.b=oZ0kRP0U; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1697908305; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=HlvuW95iDyup1VTJE32YYI7VtpdYPgzh0Z+hUfwOuiE=; b=KKHVwTSOPL6kqMIsBBiFqZO70VqW6hp8Bvty5R3ust+uNt4kety65bhm6zZAOmJy02bmcf YqLdBx9J8oq6LaK1JqMNatzW/tpY+h2GRb5GFHgpj0tb1QWVU9AaG8V4d8xt6G4+fONmmr hGtyjjJ3aEyTBnaI0QCxo8DofvC8hf/48eCGs9DK1izfYFZ6TL6cC93qEO/RygxoqoOQCY SsgEfNX1YTgyre4E7weqOmqabyRyf3hnbT037yex8X8bfLo6+dBkYxdiMEeSpCaOdhpm42 5C8tPGpxRfSvm8GaarfyFcrvj2crdklny3XpGWuL+ws3fELvt4wVzlJeQqmbPQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=guelker.eu header.s=MBO0001 header.b=oZ0kRP0U; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=none ARC-Seal: i=1; s=key1; d=yhetil.org; t=1697908305; a=rsa-sha256; cv=none; b=pWf4zFUxRGQRU1rBdv8tmqqw/66j/BPyH+XgvZ0dGchVe7Bk4HF1cpQtorjK8+6L6jNERF NnZWk1JuofFmeP1tDBdef8H8iJM8WjLB9SWH2QrN9ca9Y/B2cIqC9rdlkip4tP5Lp/GFTF ODewf+H67z5T0Q8DwnmG4qnZfnXL9yPoAZGJ6hhA04UlcNMe3wG2ozipWTGoAUIvepPtzC XaW1WBUS9Q8hKKQsI7BeFISZNiv8Arite8S+PDTG78qM/8GEeEjxdVshZ5K0rfLZospx42 UcU1KfUU8oEHSD39HR0uTcZ6x37p+DR0hs0jcyji/H5ZhypNyqonBI8cmMcMMA== Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1quF5K-00036W-LV; Sat, 21 Oct 2023 12:44:22 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1quF5I-000365-GW for emacs-orgmode@gnu.org; Sat, 21 Oct 2023 12:44:20 -0400 Received: from mout-p-102.mailbox.org ([80.241.56.152]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_CHACHA20_POLY1305:256) (Exim 4.90_1) (envelope-from ) id 1quF5G-0001GE-Gg for emacs-orgmode@gnu.org; Sat, 21 Oct 2023 12:44:20 -0400 Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:b231:465::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-102.mailbox.org (Postfix) with ESMTPS id 4SCS314fJ6z9sXk; Sat, 21 Oct 2023 18:44:13 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=guelker.eu; s=MBO0001; t=1697906653; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=HlvuW95iDyup1VTJE32YYI7VtpdYPgzh0Z+hUfwOuiE=; b=oZ0kRP0UqXJiXk+85x+Ox9JKhJ0z9wsIDthPFgNuyqCCKB6rw6AwLvmczg8TjxEpxSQsdn +befxIymZMKhyBeYLOA2vuXvTnGadXIuxf/45Q6toPNehevBKl69JjuQ33eWurNy0pFeVA Oe4tIC+zh3WE+ygjXUkFDBKN+hoUc+yVPz9I1JwqwlrMQeQ+j2nr0pUAt//H35EMNac/tB kPuODRLr+qvpfWgXBtg5sb92xfB7vOVTdXQAhXcBn5eEwvQXJteXcDlLK0c6hfRjzVVE4A eJcTSQHFyHfrL0OrmY8RGqV45+A5aiQ7whZWX6oPJcDNQd8oVrSMlUcKvB2CBQ== References: <87zg0ce6yi.fsf@guelker.eu> <87v8b0tjrj.fsf@localhost> From: Marvin =?utf-8?Q?G=C3=BClker?= To: Ihor Radchenko Cc: emacs-orgmode@gnu.org Subject: Re: Feature request: export form feed as page break Date: Sat, 21 Oct 2023 18:33:18 +0200 In-reply-to: <87v8b0tjrj.fsf@localhost> Mail-Followup-To: Ihor Radchenko , emacs-orgmode@gnu.org Message-ID: <87fs24x6w3.fsf@guelker.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4SCS314fJ6z9sXk Received-SPF: pass client-ip=80.241.56.152; envelope-from=post+orgmodeml@guelker.eu; helo=mout-p-102.mailbox.org X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -4.01 X-Spam-Score: -4.01 X-Migadu-Queue-Id: 95CD440BCB X-Migadu-Scanner: mx2.migadu.com X-TUID: Sb5iZbTedm9+ Am Samstag, dem 21. Oktober 2023 schrieb Ihor Radchenko: > In general, adding page breaks can make sense. The main concern is that > the location of page breaks may or may not be export > backend-independent. In certain scenarios, you may need to put page > breaks in one place for odt export, but in other place in LaTeX export > (for example, when page size is different in these two cases). I think this conflates two different things. On the one hand, there are typographically indicated page breaks, which appear to be those you are thinking of here. For instance, the question where to break the page within a running paragraph of text does depend on how many lines will show up on the next page; if the answer is 1, better not put a break here and rather break after the paragraph. Another example would be if you want a page break before a heading only in certain cases dependent on other material on the page or the page (size) itself. I agree that this kind of page break feature cannot be represented properly in (org) markup. On the other hand, there are semantic page breaks. The page break I described in the OP is of this kind =E2=80=93 it has been added specificall= y to hide the proposed solution from the first page and allow me to just print page 1 and hand that one to the students. For this page break, the paper size is completely irrelevant. Even if I printed on A3 for whatever reason (maybe I ran out of A4 paper), the semantic still requires the solution to be on page 2. It is this kind of page break I am referring to and which I think is representable in markup. > - In LaTeX, this is easy to achieve simply putting =3D\clearpage=3D A quick note here: \newpage and \clearpage do different things in LaTeX if there is floating material in the document. \clearpage typesets the floats and then breaks the page, whereas \newpage does not consider them. -MG --=20 Dipl.-Jur. M. G=C3=BClker | https://mg.guelker.eu | PGP: Siehe Webseite Passau, Deutschland | kontakt@guelker.eu | O<