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 SJeBIbvJuWbmYwAA62LTzQ:P1 (envelope-from ) for ; Mon, 12 Aug 2024 08:37:15 +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 SJeBIbvJuWbmYwAA62LTzQ (envelope-from ) for ; Mon, 12 Aug 2024 10:37:15 +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=1723451835; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=2qEtc93q+pjjNOhxxm2dbWA7PX9hEPhzwaY1EX1SlOE=; b=slSJQIevUKyDJlfBlH8rL4jZrXCX+qTB+jzzpQLqwApPRA0LH1nhfxNCpwkX61EnBNUB97 l44CshlZj8VpWfKfEmDMr6k1ymKrT7dF60E1UvRDMLm387VtNJhYSxNR8cRzusqZ3D++0h amaJv1DVFmfoGyeN7WziEwtYCfQ9F/KTFFRQl8BXylr5n4k+ylvzcca0CN/drSCYJGrAxJ hfrt5kiytWRGq/c6PuzR56cTCzwnWTTDYl3FOfBCFXsAoUxL9is3229UuJJ3ta54Mh158A bEIhT84KmhSIZ8PirE9enz9kxr2jb8pGHgEaokKJqAxJnJspydOxPg9dfHBEGA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1723451835; a=rsa-sha256; cv=none; b=KZxZ1AgT/d4C/pGNfeeXOa2Kdhv/hUVf0Lxam3Kg+x+sERrMjrGBazys0xvRzSyJkTj3no 3OktS0F0smEY3K6cfll/zfMO43UAtJD6uo+sTNTj/UTBiVMoMuN6oJSeQRy0tHUcA1wMZ3 omATzB8amnRuHoprRKJR+vjGCAuwYIh/R1HHILtFR8UaMu9xYdV3C4X9kR0es60WB+bTmz sNYsew95nwBgqXcHcbpJz16UnRQE32f4eiQF1ihkI15rRnZgDigHHbiDA/SKPdud5rrhw6 hTEljOKztX2Ub4lBcMzQ065Sks4nRfNCbpRWbIw8CfXAXkXOq4j2645OCHT+JQ== 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 EB916E154 for ; Mon, 12 Aug 2024 10:37:14 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sdQXC-00025F-At; Mon, 12 Aug 2024 04:36:10 -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 1sdQX9-000253-Hk for emacs-orgmode@gnu.org; Mon, 12 Aug 2024 04:36:07 -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 1sdQX4-0004n5-3K for emacs-orgmode@gnu.org; Mon, 12 Aug 2024 04:36:06 -0400 Received: by mail.selma.hfmdk-frankfurt.de (Postfix, from userid 113) id 5E0C6F61CE3; Mon, 12 Aug 2024 10:35:59 +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 32F55F60D29 for ; Mon, 12 Aug 2024 10:35:57 +0200 (CEST) Received: by selma.hfmdk-frankfurt.de (Postfix, from userid 1000) id BA30C396051B; Mon, 12 Aug 2024 10:35:56 +0200 (CEST) Date: Mon, 12 Aug 2024 10:35:56 +0200 From: Orm Finnendahl To: emacs-orgmode@gnu.org Subject: Re: multipage html output Message-ID: Mail-Followup-To: emacs-orgmode@gnu.org References: <87plr14wka.fsf@localhost> <87bk2i8w07.fsf@localhost> <87r0b2kext.fsf@localhost> <87zfpk36er.fsf@localhost> <87a5hjxjbh.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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, T_SCC_BODY_TEXT_LINE=-0.01 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.85 X-Spam-Score: -2.85 X-Migadu-Queue-Id: EB916E154 X-Migadu-Scanner: mx11.migadu.com X-TUID: P/Vdk/PDsr3J Hi, I made the changes Ihor suggested and made all docstrings compliant with checkdoc. Please check whether this is now how you imagined it. Concerning the options stored in the org-page properties rather than in info I mentioned in an earlier mail, I found out it actually doesn't really change anything substantially or clarifies/reduces the code, so I decided against it. ATM it doesn't make all that much sense to me. If we're nearing code completion, we could also start tackling the documentation. I think there should be an addition for the multipage filter in ox.el (under "Filter System") and maybe some other additions to explain the mechanism for multipage output (where?) Maybe I can also get some assessment what's needed in org-manual and what to change in order to make the doc additions proposals I made compliant with the rest of org-manual. -- Orm Am Sonntag, den 11. August 2024 um 16:44:47 Uhr (+0200) schrieb Orm Finnend= ahl: > Hi, >=20 > OK, got it, I'll check and implement everything tomorrow when I'm back on= my desk... >=20 > Am 11. August 2024 15:47:30 MESZ schrieb Ihor Radchenko : > >Orm Finnendahl writes: > > > >>> Also, as a side note, this docstring does not follow docstring > >>> conventions. Try M-x checkdoc > >> > >> I corrected it adding your suggestion explicitely. Checkdoc doesn't > >> complain about this one any more, but complains all over the place > >> with other docstrings not written by me as well, so I'm not > >> sure. Please check again. > > > >> (defvar org-export-multipage-split-functions nil > >> "List of functions applied to the parse tree. > >> The functions are applied only, when multipage output is > >> requested. They are called after the parse tree has been split > >> for multipage output. > > > >This is kind of accurate (because of the implementation details), but > >very confusing. Mostly because this docstring also serves as the > >docstring for :filter-multipage-split export option. I'd prefer to be a > >bit more explicit in the design. > > > >Maybe, instead of using the same :filter-multipage-split option both to > >perform the document splitting and to post-process it, we can introduce > >two export options: > > > >1. :multipage-split-function - the function (always one function!) to > > perform the split > > > >2. :filter-multipage - functions applied on document AST after it is > > processed by :multipage-split-function. > > > >>> I do not see `org-export-transcode-multipage' in > >>> https://github.com/ormf/org-mode/tree/org-html-multipage > >>>=20 > >>> Did you forget to push some commits? > >> > >> No, that was a typo in my mail. It should have said: > >> > >>> I factored out org-html-transcode-multipage to > >>> org-export-transcode-org-data and got rid of > >>> org-html-transcode-multipage. > > > >I think you misunderstood what I was asking about. > >My point is that `org-html-transcode-org-page' largely duplicates what > >is already done in `org-export-transcode-org-data' - processing > >'inner-templtate and 'template. My suggestion is to move generic parts > >of `org-html-transcode-org-page' to ox.el and call it > >`org-export-transcode-org-page'. > > > >--=20 > >Ihor Radchenko // yantar92, > >Org mode contributor, > >Learn more about Org mode at . > >Support Org development at , > >or support my work at >=20 > ----------------- > Prof. Orm Finnendahl > Komposition > Hochschule f=C3=BCr Musik und Darstellende Kunst > Eschersheimer Landstr. 29-39 > 60322 Frankfurt am Main