Hi Tom, t...@tsdye.com (Thomas S. Dye) writes:
> Aloha Andreas, > > Andreas Leha <andreas.l...@med.uni-goettingen.de> writes: > >> Bastien <b...@gnu.org> writes: >> >>> Nicolas Goaziou <n.goaz...@gmail.com> 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
