Before I go on, I continue to be fascinated by the observation
that, each time the we really need pictures and fancy
formatting and need them frequently argument comes up, the vast
majority of those who make it most strongly are people whose
contributions to the IETF -- in designer, editor,
Lars-Erik Jonsson (LU/EAB) wrote:
Before I go on, I continue to be fascinated by the observation
that, each time the we really need pictures and fancy
formatting and need them frequently argument comes up, the vast
majority of those who make it most strongly are people whose
contributions to
--On Thursday, 12 January, 2006 12:28 +0100 Lars-Erik Jonsson
\\(LU/EAB\\) [EMAIL PROTECTED] wrote:
Before I go on, I continue to be fascinated by the observation
that, each time the we really need pictures and fancy
formatting and need them frequently argument comes up, the
vast majority
On 1/12/06, John C Klensin [EMAIL PROTECTED] wrote:
increasing experience within the IETF and with our style of
developing and working on documents (not just publishing them)
tends to cause both patience and respect for the ASCII graphics
and formats to rise.
I'm surprised folks are
John, Stewart and others,
I believe some might have taken my previous note more
personally than intended, as well as John's. As also
made clear by John below, we both looked at this with
a significantly longer time-perspective than just the
last weeks or months, as these issues have been brought
*
* Under those conditions, our precedents are that you can probably
* convince the WG/WGchairs/ADs, and eventually the RFC Editor,
* that a PDF document containing a picture of the Mona Lisa and an
* ASCII document with
*
* _-
* / \
*
We need to get out this ancients vs moderns dispute. Ancients saying
they have no experience of actual need by moderns, and moderns saying
this is because the ancient culture does not permit it.
Is there an objection to quote non-ascii documents hyperlinks? I suppose not.
Why not to just to
*
* Why not to just to proceed step by step and experiment? Let create an
* optional non-ascii art RFC-Editor repositories, for images quoted in
* RFCs. This will not permit non-ASCII art to be normative but will
* permit non-ASCII art to be _better_ descriptive in a first time.
At 18:49 06/01/2006, Bob Braden wrote:
*
* Why not to just to proceed step by step and experiment? Let create an
* optional non-ascii art RFC-Editor repositories, for images quoted in
* RFCs. This will not permit non-ASCII art to be normative but will
* permit non-ASCII art to be
--On Thursday, 05 January, 2006 17:01 + Stewart Bryant
[EMAIL PROTECTED] wrote:
...
I find it interesting that it has not been taken
advantage of more often (and, for the record, I'm one of those
who has taken advantage of it). When it has been done for
artwork purposes, the artwork in
10 matches
Mail list logo
