From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Leha Subject: Re: [PATCH] Re: \newpage in HTML export Date: Fri, 03 Jan 2014 21:10:19 +0100 Message-ID: <87iou0kes4.fsf@med.uni-goettingen.de> References: <8738moubd4.fsf_-_@ericabrahamsen.net> <8738mo68fi.fsf@gmail.com> <3389069.jUrlGMUlNA@descartes> <87a9gu6t92.fsf@gmail.com> <87k3fym54f.fsf@ericabrahamsen.net> <87li0dvr4d.fsf@med.uni-goettingen.de> <87wqixhu66.fsf@gmail.com> <871u0pcbw0.fsf@bzg.ath.cx> <87mwjckgnf.fsf@med.uni-goettingen.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41659) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzB4y-0002cd-VS for emacs-orgmode@gnu.org; Fri, 03 Jan 2014 15:10:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VzB4u-0008J8-18 for emacs-orgmode@gnu.org; Fri, 03 Jan 2014 15:10:48 -0500 Received: from plane.gmane.org ([80.91.229.3]:47363) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VzB4t-0008J2-PR for emacs-orgmode@gnu.org; Fri, 03 Jan 2014 15:10:43 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VzB4m-0006b6-Jk for emacs-orgmode@gnu.org; Fri, 03 Jan 2014 21:10:36 +0100 Received: from vpn-2006.gwdg.de ([134.76.2.6]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Jan 2014 21:10:36 +0100 Received: from andreas.leha by vpn-2006.gwdg.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 03 Jan 2014 21:10:36 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi Tom, tsd@tsdye.com (Thomas S. Dye) writes: > Aloha Andreas, > > Andreas Leha writes: > >> Bastien writes: >> >>> Nicolas Goaziou writes: >>> >>>>> So in short: If page breaks are not in org directly many people will >>>>> end up with inferior and/or less portable org files. >>>> >>>> For the record, after thinking about it, I'd rather stay away from >>>> invisible characters in Org syntax, would it be page breaks or >>>> non-breaking spaces. >>> >>> FWIW I fully support not using invisible chars in Org syntax. >> >> This follows up on just a side aspect in this thread that is (partly) >> separate from its subject. >> >> >> Just to wrap the thread up in my words: >> >> 1. Cross-backend (or more cross-backend) support of \newpage built into >> Org directly was disapproved in favor of a less portable filter based >> solution [fn:1]. > > Could you expand on what you mean by "less portable"? I'm interested in > portability from a reproducible research perspective and want to avoid > habits that don't port well to other researchers' systems. > I did not want to include these words in the first place. The words 'less portable' are too strong here. You won't be affected, since you ship your emacs / Org configuration with the document, IIUC. (Which is the only possible way to achieve something like reproducibility with Org...) In that case you can simply include such a filter in that configuration. The non-portable part comes from the need to share that filter. Anybody without that filter will not be able to export your document in the intended way. Just to clarify: It is a very small thing and I am very much happy with using a filter based approach here. > Happy New Year! Same to you! Regards, Andreas