[rfc-i] Pagination requirements

Joe Hildebrand jhildebr at cisco.com
Wed May 23 12:33:24 PDT 2012

On 5/23/12 1:09 PM, "Joe Touch" <touch at isi.edu> wrote:

> The claim was that we needed a vintage line printer. We proved that
> isn't the case. Whether this is a goal of the format or not, it's not a
> limitation.

The claim was intended to be that you needed a vintage line printer for it
to not require gyrations.  I apologize if I didn't make that clear enough.
Importing into a different application and making a ton of formatting tweaks
definitely count as gyrations to me.

> Now you want to print from a browser. Browsers are for browsing, not
> printing - try going to an arbitrary web page and printing it and see
> what you get.

A nicely formatted page that includes all of the information I saw on the
screen, particularly if the author was careful about how they constructed
the page.

> There might be a solution in here somewhere, but it involves changing
> browsers to know more about how to render printouts. I'm not sure that's
> a useful requirement.

Or not being so hung up on the absolute positioning of things on the page
(including getting rid of page numbers as anchors) that we don't need
anything more than what browsers currently do.  A slight shift in
requirements from "the requirement is this particular solution that we
currently have" to "the requirement is this use pattern" is all that it

> On 5/23/2012 11:58 AM, Joe Hildebrand wrote:
>> If the goal is to prevent anyone who isn't a member of the club from
>> participating, the underlying will work just fine.
>> I don't see that as a goal of the format, however.
>> On 5/23/12 12:43 PM, "Joe Touch"<touch at isi.edu>  wrote:
>>> On 5/23/2012 11:29 AM, Martin Rex wrote:
>>>> Joe Touch wrote:
>>>>> Brian E Carpenter wrote:
>>>>>> Joe Hildebrand wrote:
>>>>>> ...
>>>>>>> Printing the current format is an absolute mess, unless you
>>>>>>> have a vintage line printer.
>>>>>> Not true. I regularly print I-Ds and occasionally RFCs in
>>>>>> "booklet" format on all kinds of printers (as long as they
>>>>>> support that format of course, but it seems to be widespread
>>>>>> on duplex printers).
>>>>> FWIW, MS Word imports .txt files with ^L's fine, and respects them as
>>>>> page breaks.
>>>> Now that you mention it.
>>>> Wordpad (which is part of Microsoft Windows), also understands
>>>> and respects FormFeed (^L) characters.  On Windows XP/2003,
>>>> it will directly print RFCs correctly (due to the default 10cpi
>>>> font size and default 1inch left and right margin).
>>>> WordPad in Windows 7 uses different defaults. (1 1/4 left and right
>>>> margins and 11cpi font size), so what you would have to do to make
>>>> it print
>>>>      - Drop-down Menu "Page Setup" change the left&   right margins
>>>>        to 1inch (25.4mm) -- that setting is memorized through restarts
>>> also turn off page numbers there
>>> also turn off word wrap (just in case you get an ID/RFC that
>>> has longer lines)
>>> both the above are kept thought restarts
>>>>      - after loading of the rfcXXXX.txt in Win7 Wordpad,
>>>>        use "Select All" (Keyboard Shortcut<Ctrl-A>)
>>>>        and then change the font size in the drop-down list next to the
>>>>        font name in the Toolbar(Ribbon) from its "11"cpi size to "10" cpi.
>>> FWIW, any size 10 or below works. You *can* pick a smaller size,
>>> though it has little benefit.
>>>>      - print.
>>>> I boldly assume that this is within the skill level expected
>>>> from the target audience of IETF RFCs.
>>>> -Martin
>>> _______________________________________________
>>> rfc-interest mailing list
>>> rfc-interest at rfc-editor.org
>>> https://www.rfc-editor.org/mailman/listinfo/rfc-interest

Joe Hildebrand

More information about the rfc-interest mailing list