[rfc-i] Fwd: New Version Notification for draft-flanagan-plaintext-00.txt

Thomas Clausen ietf at thomasclausen.org
Fri Jun 27 08:31:35 PDT 2014

On Jun 27, 2014, at 12:29, Dearlove, Christopher (UK) <chris.dearlove at baesystems.com> wrote:

> Now that's just deliberately insulting.
> No one has suggested not being able to put things on an iPad.

I just want to jump in here….most of my “reading and annotating I-Ds and RFCs” is done on an iPad. I use GoodReader and the PDF version of I-D/RFCs.

That which is not done on an iPad is done on a print-out (paginated, A4, not fan-fold) — often, of the PDF.

I’d guess that the split is roughly 70% — 30% between the two above.

So, we actually can already do that.

[I’ve event got a hacked-up tool that will do “OLD: … NEW: …” style plain-text for sending via email to authors  (and, which indicates the page number, too, of the proposed edit) from an annotated PDF, but it’s not quite ready for wide consumption just yet…I do hope that whatever the new format will be won’t break that … ]

> However it also remains useful to put things reliably, and formatted at least to the point of not splitting things cross pages, on paper. Fanfold is just an transparent attempt to make an opinion not your own look archaic.
> And this got raised because you may not want paper, but some of us do,

And even when not actually using paper, I still like the paginated format and the not-splitting with which  Chris is concerned.


> and you at least now appear to be ready to steamroller those who disagree with you.
> At the moment what appears to be on offer is
> - Text, but freeflowing and not suitable (tables and figures will break).
> - HTML, where some (but definitely not all) browsers might offer what you want, but at the least not guaranteed.
> - PDF, where format is stated as not defined yet. (It's still my best hope, and I think people planning it are thinking of this issue, maybe more than they were.)
> I was going to let this rest, I'd made my point, but your response stirred me to this.
> -- 
> Christopher Dearlove
> Senior Principal Engineer, Communications Group
> Communications, Networks and Image Analysis Capability
> BAE Systems Advanced Technology Centre
> West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
> Tel: +44 1245 242194 |  Fax: +44 1245 242124
> chris.dearlove at baesystems.com | http://www.baesystems.com
> BAE Systems (Operations) Limited
> Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants, GU14 6YU, UK
> Registered in England & Wales No: 1996687
> -----Original Message-----
> From: John Levine [mailto:johnl at taugh.com] 
> Sent: 26 June 2014 19:00
> To: rfc-interest at rfc-editor.org
> Cc: Dearlove, Christopher (UK)
> Subject: Re: [rfc-i] Fwd: New Version Notification for draft-flanagan-plaintext-00.txt
> ----------------------! WARNING ! ---------------------- This message originates from outside our organisation, either from an external partner or from the internet.
> Consider carefully whether you should click on any links, open any attachments or reply.
> Follow the 'Report Suspicious Emails' link on IT matters for instructions on reporting suspicious email messages.
> --------------------------------------------------------
> In article <B31EEDDDB8ED7E4A93FDF12A4EECD30D402F6675 at GLKXM0002V.GREENLNK.net> you write:
>> No one I've noticed has suggested that all formats should have line numbers, be easily printable etc.
> All of these issues have come up before, often more than once.  It could save considerable time if you'd review the past year's discussions on this list.
> As noted the last several times we talked about this particular point, these days, a lot of us are much more interested in formats we can read and perhaps annotate on an iPad or Android tablet than ones that might be easier to print on fanfold paper.
> R's,
> John
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
> _______________________________________________
> rfc-interest mailing list
> rfc-interest at rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-interest

More information about the rfc-interest mailing list