Re: [iola-conversion-tool] Trimming Whitespace from the beginning of DISCUSS and COMMENT

Russ Housley <housley@vigilsec.com> Thu, 01 March 2012 15:20 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: iola-conversion-tool@ietfa.amsl.com
Delivered-To: iola-conversion-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83DDF21E81C1 for <iola-conversion-tool@ietfa.amsl.com>; Thu, 1 Mar 2012 07:20:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.551
X-Spam-Level:
X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dXP9O76X0WKi for <iola-conversion-tool@ietfa.amsl.com>; Thu, 1 Mar 2012 07:20:11 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 118C021E81C3 for <iola-conversion-tool@ietf.org>; Thu, 1 Mar 2012 07:19:53 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 01E47F2401E; Thu, 1 Mar 2012 10:19:56 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id DtVDgkKefrdW; Thu, 1 Mar 2012 10:19:43 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 014A39A471B; Thu, 1 Mar 2012 10:19:54 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4F4F5E66.1090804@levkowetz.com>
Date: Thu, 1 Mar 2012 10:19:50 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <7CEB8F9D-5024-4276-BCDD-8FB7EDE8570D@vigilsec.com>
References: <9783DA0B-4717-476B-8806-F26A1A415802@vigilsec.com> <4F4D4129.3020908@nostrum.com> <4F4F5E66.1090804@levkowetz.com>
To: Henrik Levkowetz <henrik@levkowetz.com>
X-Mailer: Apple Mail (2.1084)
Cc: iola-conversion-tool@ietf.org, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [iola-conversion-tool] Trimming Whitespace from the beginning of DISCUSS and COMMENT
X-BeenThere: iola-conversion-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the IOLA / DB Schema Conversion Tool Project <iola-conversion-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iola-conversion-tool>, <mailto:iola-conversion-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iola-conversion-tool>
List-Post: <mailto:iola-conversion-tool@ietf.org>
List-Help: <mailto:iola-conversion-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iola-conversion-tool>, <mailto:iola-conversion-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 15:20:22 -0000

On Mar 1, 2012, at 6:32 AM, Henrik Levkowetz wrote:

> Hi Russ, Robert,
> 
> I've entered this into the issue tracker as #781:
>  http://trac.tools.ietf.org/tools/ietfdb/ticket/781
> 
> On 2012-02-28 22:03 Robert Sparks said:
>> I agree with a first step of getting closer to where we were.
>> 
>> That said, prior to conversion, the reflow mechanics, particularly when 
>> preparing email, have been
>> consistently in my way. Can we move to something that performs reflow by 
>> default, but allows us
>> to turn it off and provide our own formatting when it's the best way to 
>> get the information across?
> 
> That should be possible, but may move the re-flowing operation from
> entry to presentation, where I believe we have it now, in order to not
> mess with what's entered into the database.
> 
> Can you give me some examples of where reflowing is messing things up?
> 
> If re-flowing is only applied for very long lines and on presentation,
> then anything you enter with proper formatting should be left alone.
> I'll check the code to see if this is the way it's being handled now.
> 
>> RjS
>> 
>> On 2/28/12 2:58 PM, Russ Housley wrote:
>>> Prior to the conversion, an AD entering text in the discuss or
>>> comment box had greater control over the formatting.  The new form
>>> seems to trim whitespace from the front of the provided text.
> 
> Ok; we should check whether this is done on entry or at presentation
> time -- do you have an example to look at?

NEW: https://datatracker.ietf.org/doc/draft-ietf-netext-pmip-lr/ballot/

OLD: https://datatracker.ietf.org/doc/draft-ietf-csi-dhcpv6-cga-ps/ballot/

Russ