From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms13.migadu.com with LMTPS id YG1lBNIIiWbFyAAA62LTzQ:P1 (envelope-from ) for ; Sat, 06 Jul 2024 09:05:22 +0000 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id YG1lBNIIiWbFyAAA62LTzQ (envelope-from ) for ; Sat, 06 Jul 2024 11:05:22 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=hfmdk-frankfurt.de (policy=none); 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" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1720256722; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post; bh=o24A/+Ymv6HqXZxXSu3BC/keFyI3SHHLh2Vl2NuW8iM=; b=nC6NFgNaH2Gh6NXONfGaQEKtft5E8DyT9Csn2pBl/lZ8cZpStwbHnc4fXrQv1aNxrPdjMg JaIkq0HUzGUJywYOUvfpCbjghYVgGgrNn9s7bCbS1bRmVDygeKkh96szV92SzCQtMXu/Pl hi4O84oX0/khicqmg9ntwQ5FG4hHUvHgNG2Q6Vi1bWOCbIT+ImCa0UvNfMpV5/AZWgPqYa PDswwBr5pyAggRHZ0PUgtii61RY2ieDFiQ7FY591NNC5bFGFPYredqNMuWH1C8g9eKAZWa WlEu7rfrf7jka8iEyqJgjBtX/iPUXbgQfbl9+Sp8AaOPOvAsRuBUwpCF83Zc8A== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1720256722; a=rsa-sha256; cv=none; b=EevZTh8twExLbOJb9QUg6q5w1IZkuW9TFnsMDqRRHcn4M1AWZHLR6pH1pc76k+v0lnfaFr bjpkev+OzNgv+eQFqTiyTMY3wgU6dbur/CFDYs0L6nz9iqqy+TexzG26tCutxokjKIYSWL WgVqsRGvW36IUyRH5Gi3fgf1rKMDskmvbiT2H5ZUDg4Ge61IQj77+Z5MJxBKr3oPSxe/qZ +VKqjVaJgqfdBw66zMfqMwj6VrUJ397qo8f4/FJJLfrM8yYNFoxH58InqLQ4pCeiOG/IhQ 2Sl0ZTZQnBgjbK3Zowp9G2gKvVO9mTjTDwSlITWiNpVTcLNGAoOCn+tyDWn7pg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=hfmdk-frankfurt.de (policy=none); 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" 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 BD80F634E8 for ; Sat, 06 Jul 2024 11:05:21 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sQ1LG-0002Yg-SX; Sat, 06 Jul 2024 05:04:26 -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 1sQ1LE-0002YT-JF for emacs-orgmode@gnu.org; Sat, 06 Jul 2024 05:04:24 -0400 Received: from www.selma.hfmdk-frankfurt.de ([46.4.92.145] helo=mail.selma.hfmdk-frankfurt.de) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sQ1LC-0006hw-RM for emacs-orgmode@gnu.org; Sat, 06 Jul 2024 05:04:24 -0400 Received: by mail.selma.hfmdk-frankfurt.de (Postfix, from userid 113) id A4206F61D24; Sat, 6 Jul 2024 11:04:17 +0200 (CEST) Received: from selma.hfmdk-frankfurt.de (ip-037-201-128-004.um10.pools.vodafone-ip.de [37.201.128.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (Client did not present a certificate) by mail.selma.hfmdk-frankfurt.de (Postfix) with ESMTPSA id 85207F609F1 for ; Sat, 6 Jul 2024 11:04:15 +0200 (CEST) Received: by selma.hfmdk-frankfurt.de (Postfix, from userid 1000) id 2D5753960569; Sat, 06 Jul 2024 11:04:15 +0200 (CEST) Date: Sat, 6 Jul 2024 11:04:15 +0200 From: Orm Finnendahl To: Org Mode List Subject: Re: multipage html output Message-ID: Mail-Followup-To: Org Mode List References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Disclaimer: Why are you listening to me? X-Operating-System: GNU/Linux Organization: Hochschule =?utf-8?B?ZsO8?= =?utf-8?Q?r?= Musik und Darstellende Kunst Frankfurt, Frankfurt, Germany Received-SPF: pass client-ip=46.4.92.145; envelope-from=orm.finnendahl@selma.hfmdk-frankfurt.de; helo=mail.selma.hfmdk-frankfurt.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, 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-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -2.79 X-Spam-Score: -2.79 X-Migadu-Queue-Id: BD80F634E8 X-Migadu-Scanner: mx11.migadu.com X-TUID: avF8SXp7FZvc Hi, Am Samstag, den 06. Juli 2024 um 07:47:43 Uhr (+0200) schrieb Pedro Andres Aranda Gutierrez: > Sorry for bumping in, I've been more off than on in the last couple of > weeks... > Just a stupid question: have you considered any marker to force a page > break? > That would make this functionality portable to other exporters like LaTeX, > where > you can force a page break with \clearpage or \cleardoublepage. although this is of course possible, currently I'm not planning to implement it. Regarding html export I see some problems with that idea: 1. It would either open a new can of worms if this page would be added to the toc with all sorts of ensuing problems like naming, etc. and getting out of sync with the Latex document's toc. or 2. Those additinal pages don't get added to the toc and are only reachable by navigation elements, which I consider suboptimal (and you'd still have to name them). In any case, currently I'm facing many problems concerning the glorious hairy details and am glad if I can sort them out in a way that they are general enough to be added to ox. Adding additional engines to handle page breaks the way you envision should then be feasible without reinventing the wheel. -- Orm