Re: [O] [PATCH] Re: \newpage in HTML export

[Thomas S. Dye]

Aloha Andreas,

Andreas Leha <address@hidden> writes:

> Bastien <address@hidden> writes:
>
>> Nicolas Goaziou <address@hidden> 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.

Happy New Year!

-- 
Thomas S. Dye
http://www.tsdye.com