[rfc-i] Two issues with draft-flanagan-plaintext-00
Joel M. Halpern
jmh at joelhalpern.com
Mon Jun 30 18:04:38 PDT 2014
The requirements RFC says that we will support printing with page
numbers. That does not mean printing of the .txt with page numbers.
This whole discussion has been a rehash of what went before.
I, for one, am perfectly happy to let the various tools developers
figure out how they think it is best to meet the printing requirement
rather than heading off and designing for some requirements other than
the ones we agreed to.
On 6/30/14, 8:58 PM, Dave Crocker wrote:
> On 6/27/2014 8:32 PM, Brian E Carpenter wrote:
>> 2. The lack of pagination turns out to be much more annoying than
>> I expected. Even in a short draft, I get a couple of widowed
>> lines of text, and at least in my setup, there's no margin at
>> the bottom of the page. (The lack of page numbers and running
>> headers and footers is no loss, IMHO.)
>> Given that without pagination, there is nothing to stop artwork
>> being mangled either, I think we need pagination - but we don't
>> need page numbers; just the form feeds.
> I think it's worth going back to Brian's original observation and
> suggestion and considering it carefully and narrowly, since the
> suggestion is actually quite narrow.
> I summarize it as:
> 1. Drop headers and footers
> 2. Have the txt generating engine inject FF intelligently, in order
> to get better placement of pagebreaks, for systems honoring the
> long-standing page break signal.
> I believe all of the negative comments posted so far fall into only a
> few categories:
> 1. Not all (or, at least not very many) applications support FF
> 2. Headers and footers in the middle of the page are distracting
> 3. txt is evil, or at least archaic.
> #2, of course, is irrelevant, since it is not part of his suggestion.
> #3 is selling past the sale, beating a dead topic, and otherwise out of
> scope for his narrow and constructive suggestion.
> Worse, what's been missed is that Brian's suggestion falls somewhere
> between useful and, at worst, benign, and for very little cost.
> It does not cause problems on systems that ignore FFs; we have no
> reports of its being mishandled. And it does produce better results on
> systems that honor FF.
More information about the rfc-interest