On 09-07-02 1:00 AM, Randy Presuhn randy_pres...@mindspring.com wrote:
One of the advantages of nroff input is that it *is* human readable. (To me
it seems much easier to read than HTML, but that's not the issue here.)
To generate formatted output (in a variety of possible formats) the
On 2009-07-01 22:38 Martin Rex said the following:
While I participated IETF Meetings in 1995-98, I often used pstools to
create printed copies (2-up) of RFCs and Internet Drafts for reading
while travelling and during meetings (didn't have a laptop).
I used a wrapping perl-script
Have a look at Dave Mills recent remarks on the NTP list :
https://lists.ntp.org/pipermail/ntpwg/2009-June/001519.html
Due to his diminished eyesight he can't handle the text
of the document he is co-authoring without significant preprocessing.
Y(J)S
-Original Message-
From:
On 2 jul 2009, at 10:47, Yaakov Stein wrote:
Due to his diminished eyesight he can't handle the text
of the document he is co-authoring without significant preprocessing.
Ok if we're going to have this discussion again:
PDF is a way to display documents on the screen the same way that
The limitations of ASCII format have been discussed here numerous times.
For example, see the lengthy thread last year on draft-ash-alt-formats (now
expired).
Many people have proposed modern approaches that comply with the constraints.
Going back a generation or two to nroff seems to me to be a
Douglas Otis dotis at mail dash abuse dot org wrote:
Word's closed code is continuously changing. Availability of this
closed application depends upon OS compatibility and version
regressions. Both are moving targets. In addition, Word formats
permit inclusion of potentially destructive
Doug Ewell wrote:
Douglas Otis dotis at mail dash abuse dot org wrote:
Word's closed code is continuously changing. Availability of this
closed application depends upon OS compatibility and version
regressions. Both are moving targets. In addition, Word formats
permit inclusion of
On Thu, Jul 2, 2009 at 2:01 AM, Iljitsch van Beijnumiljit...@muada.com wrote:
A much better solution would be HTML, if it's sufficiently constrained. HTML
allows for the reflowing of text, solving issues with text and screen sizes.
It's also extremely widely implemented, so it's easy to
Tim Bray wrote:
On Thu, Jul 2, 2009 at 2:01 AM, Iljitsch van Beijnumiljit...@muada.com wrote:
A much better solution would be HTML, if it's sufficiently constrained. HTML
allows for the reflowing of text, solving issues with text and screen sizes.
It's also extremely widely implemented, so
At 10:19 PM -0700 7/1/09, Douglas Otis wrote:
for wanting more than just plain text documents is to permit
inclusion of charts, graphs, and tables, for a visual society
It seems to me that where this discussion has faltered before is
on whether this is, in fact, a requirement. In the past,
On Jul 2, 2009, at 12:16 PM, Ted Hardie wrote:
At 10:19 PM -0700 7/1/09, Douglas Otis wrote:
for wanting more than just plain text documents is to permit
inclusion of charts, graphs, and tables, for a visual society
It seems to me that where this discussion has faltered before is
on
On 2 jul 2009, at 17:05, Stewart Bryant wrote:
A much better solution would be HTML
This seems obviously true everywhere outside the IETF mailing list.
The showstopper has always been with figures which need to do in
separate files. How do you manipulate the collection of files as a
Iljitsch,
That box shows up as complete gibberish in a plain-text mail reader
(pine in my case), which sort of proves the point about ASCII. What
you sent was certainly not ASCII.
Ole
Ole J. Jacobsen
Editor and Publisher, The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972
Iljitsch van Beijnum wrote:
On 2 jul 2009, at 17:05, Stewart Bryant wrote:
A much better solution would be HTML
This seems obviously true everywhere outside the IETF mailing list.
The showstopper has always been with figures which need to do in
separate files. How do you manipulate
On Jul 2, 2009, at 9:22 AM, Marshall Eubanks wrote:
On Jul 2, 2009, at 12:16 PM, Ted Hardie wrote:
At 10:19 PM -0700 7/1/09, Douglas Otis wrote:
for wanting more than just plain text documents is to permit
inclusion of charts, graphs, and tables, for a visual society
It seems to me that
To save time, I would suggest adopting the Patent Office rules on
Perpetual Motion. People advocating for a change to facilitate figures
(or to allow complicated math, such as tensor analysis) should have an
existence proof, i.e., a document that requires the change to be
published. (A
On Jul 2, 2009, at 2:01 PM, Stewart Bryant wrote:
To save time, I would suggest adopting the Patent Office rules on
Perpetual Motion. People advocating for a change to facilitate
figures (or to allow complicated math, such as tensor analysis)
should have an existence proof, i.e., a
On 7/2/09 at 4:05 PM +0100, Stewart Bryant wrote:
Tim Bray wrote:
On Thu, Jul 2, 2009 at 2:01 AM, Iljitsch van
Beijnumiljit...@muada.com wrote:
A much better solution would be HTML, if it's sufficiently constrained.
Or, gee, we could generalize to a very constrained XML
Hi -
From: Stefan Santesson ste...@aaa-sec.com
To: Donald Eastlake d3e...@gmail.com; IETF Discussion Mailing List
ietf@ietf.org
Sent: Wednesday, July 01, 2009 3:42 PM
Subject: Re: More liberal draft formatting standards required
How do you translate the .nroff formatted document
[I am sorry if you receive this more than once.]
Dear Colleagues,
The Internet Society has announced that it is seeking applications
for the next round of the ISOC Fellowship to the IETF program. The
program offers engineers from developing countries fellowships that
fund the cost of
20 matches
Mail list logo
