Re: Image attachments to ASCII RFCs (was: Re: Last Call: 'Proposed Experiment: Normative Format in Addition to ASCII Text' to Experimental RFC (draft-ash-alt-formats))

John C Klensin <john-ietf@jck.com> Tue, 20 June 2006 15:41 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsiMD-0004zI-Bm; Tue, 20 Jun 2006 11:41:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsiMC-0004zD-HV for ietf@ietf.org; Tue, 20 Jun 2006 11:41:36 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FsiMB-0006gU-2I for ietf@ietf.org; Tue, 20 Jun 2006 11:41:36 -0400
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1FsiM5-000Kr4-6V; Tue, 20 Jun 2006 11:41:29 -0400
Date: Tue, 20 Jun 2006 11:41:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Message-ID: <77E72E161804CCBBE14D95C9@p3.JCK.COM>
In-Reply-To: <FB074F84-1F84-445B-BF55-E1EF27C7F178@muada.com>
References: <200606191632.JAA21463@gra.isi.edu> <B383FFD572C6573F84C6CDA8@p3.JCK.COM> <7CF65D0D-8184-416D-9A2B-37570CAAF723@muada.com> <01M3TF1A05EY0049K2@mauve.mrochek.com> <FB074F84-1F84-445B-BF55-E1EF27C7F178@muada.com>
X-Mailer: Mulberry/4.0.4 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: Ned Freed <ned.freed@mrochek.com>, IETF-Discussion Discussion <ietf@ietf.org>
Subject: Re: Image attachments to ASCII RFCs (was: Re: Last Call: 'Proposed Experiment: Normative Format in Addition to ASCII Text' to Experimental RFC (draft-ash-alt-formats))
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org


--On Tuesday, 20 June, 2006 12:00 +0200 Iljitsch van Beijnum
<iljitsch@muada.com> wrote:

> On 20-jun-2006, at 1:07, Ned Freed wrote:
>...
>> I've tried using change bars and other fancier
>> tools,   but I have
>> concluded they're more trouble than they're worth.
> 
> Then you haven't been doing it right... If you use Word, for
> instance  (but Open Office has the same functionality) you can
> set up "track  changes" and "highlight changes when editing"
> or words to the same  effect, and then you'll see text that's
> added in a different color  depending on who added it, and you
> can reject or accept changes made  by others. You can also
> easily skip to the next edit. I can't imagine  two or more
> people working on the same document without this
> functionality.

Hmm.   With Word, for instance, virtually every correction to
the text results in a huge clutter of change-tracking notes
about format changes and similar drivel.  For many documents, it
makes the S/N ratio just miserable.   If there were a "track
substantive textual changes only" option, an "ignore format
changes" one, or some sort of "accept all format, font, and
style changes" command, I'd probably agree with you about
utility.  But, given the reality of those systems today, I tend
to agree with Ned, even though I like a feature of those system
that you didn't mention (the ability to insert comments whose
appearance in the output can easily turned on and off.  <cref>
and some processing options comes close, but isn't quite the
same).

>> My immediate thought in response to all this is "what a
>> colossal   waste of
>> time". I want to focus on document content, not stylistic
>> frills   and irrelevant
>> minutiae. That's what the RFC Editors gets the big bucks to
>> do... I   therefore
>> want a tool that lets me engage in semantic markup with as
>> little   attention
>> paid to layout issues as possible.
> 
> And that's exactly what the style mechanism is for: you can
> indicate  headings of different levels (= generate numbering
> and table of  contents automatically), have different kinds of
> lists (bulleted,  numbered) and so on.

If it worked, that would be how it would work.  My own
experience is that it is very hard to get it to work well.  To
take a handy example, try to generate a cross reference to a
heading that hasn't been generated with a built-in style in Word
(2000/ XP/ 2003). 

>...
>>> That is not my experience. Figures are very hard to get
>>> right, they very often require edits.
> 
>> It depends on what sort of edits you're talking about. Both
>> figures and equations move things away from pure semantic
>> markup and towards presentation specifics. It's unavoidable,
>> and once you enter the   presentation
>> realm the list of possible tweaks to make things just a
>> little bit better often seems endless.
> 
> I'm talking about stuff like "the text in this box should be A
> but  it's B" and "there shouldn't be a line between those two
> boxes".

But those are precisely the things that, in our environment, one
wants the author to get right and the RFC Editor to not mess
with.

    john


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf