Re: [ogpx] Cable Beach + VWRAP update

Carlo Wood <carlo@alinoe.com> Wed, 20 January 2010 14:50 UTC

Return-Path: <carlo@alinoe.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E25D13A6942 for <ogpx@core3.amsl.com>; Wed, 20 Jan 2010 06:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.367
X-Spam-Level:
X-Spam-Status: No, score=-0.367 tagged_above=-999 required=5 tests=[AWL=-0.426, BAYES_05=-1.11, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eyr-MUeoUt92 for <ogpx@core3.amsl.com>; Wed, 20 Jan 2010 06:50:57 -0800 (PST)
Received: from viefep18-int.chello.at (viefep18-int.chello.at [62.179.121.38]) by core3.amsl.com (Postfix) with ESMTP id F028B3A6855 for <ogpx@ietf.org>; Wed, 20 Jan 2010 06:50:47 -0800 (PST)
Received: from edge03.upc.biz ([192.168.13.238]) by viefep18-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20100120145042.SYUM8510.viefep18-int.chello.at@edge03.upc.biz>; Wed, 20 Jan 2010 15:50:42 +0100
Received: from mail9.alinoe.com ([77.250.43.12]) by edge03.upc.biz with edge id Xqqg1d03B0FlQed03qqhYT; Wed, 20 Jan 2010 15:50:42 +0100
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.71) (envelope-from <carlo@alinoe.com>) id 1NXbtI-0004ba-20; Wed, 20 Jan 2010 15:50:40 +0100
Date: Wed, 20 Jan 2010 15:50:40 +0100
From: Carlo Wood <carlo@alinoe.com>
To: Morgaine <morgaine.dinova@googlemail.com>
Message-ID: <20100120145040.GA17377@alinoe.com>
References: <62BFE5680C037E4DA0B0A08946C0933DC4A74D40@rrsmsx506.amr.corp.intel.com> <e0b04bba1001152009k5885cb07r9108626237d9f5ea@mail.gmail.com> <OFDFA05603.517E9F75-ON852576AF.0062AE14-852576AF.006416D6@us.ibm.com> <e0b04bba1001190011iacead6jaa7a68f22de81a97@mail.gmail.com> <20100119131143.GA21575@alinoe.com> <e0b04bba1001191627s12d06fdbg6145e56a8d94b548@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <e0b04bba1001191627s12d06fdbg6145e56a8d94b548@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: "ogpx@ietf.org" <ogpx@ietf.org>
Subject: Re: [ogpx] Cable Beach + VWRAP update
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jan 2010 14:50:58 -0000

On Wed, Jan 20, 2010 at 12:27:00AM +0000, Morgaine wrote:
> On Tue, Jan 19, 2010 at 1:11 PM, Carlo Wood <carlo@alinoe.com> wrote:
> 
> Morgaine, with long posts like this, it's a problem for me that
> I cannot see who wrote what.
> 
> I ask you to add some quotation character, at least, or better,
> that you do not use html posts, but reply in plain text. This will
> also help for archiving purposes imho.
> 
> 
> Carlo, both the Gmail copy of my reply to David and the IETF web archive
> copy at http://www.ietf.org/mail-archive/web/ogpx/current/msg00729.html have
> quotation blocks defined and identified with their originator, and they both
> match each other too.
> 
> This makes me think that you have a problem with your mail client, as it
> appears to be losing information somewhere.  The post that you've enclosed
> does suggest this, as it shows David's text and mine at the same level of
> indentation, which is incorrect.  It's clearly not what I sent, since the
> IETF archive copy shows the post structured properly.
> 
> I've also asked others how they see the post, and they confirm that the
> indented quotation blocks are present.  While Gmail is far from perfect,
> it's rather widely used, so I doubt that there's a major problem there.

If they are using html, of course they do.

> If you know of some Gmail setting that might help, I would be happy to try
> it out.  I won't switch all replies to plain text though unless it's
> officially required here and everyone else on the list does too.  Personally
> I use block quoting, italics, bold and URLs as my only Gmail "rich"
> features, which is pretty minimal and much less than some others are using.
> That tiny set is completely IETF mailman compatible, as the above URL
> proves.

I sent myself a post from gmail using "rich text", a reply to one of the posts
here and then sending it to me only, and that results in indentation for the
quoted text.

Your posts are the only ones that have no indentation or quotation
marks for quoted text... Sorry, but it should work good enough with
gmail.

I looked at the HTML of your posts and it looks like this:

<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br></blockquote><div style="margin-left: 40px;"><font face="sans-serif" size="2">I read John&#39;s post as &quot;This is
what we have built, how it works, and how you can think about it mapping
onto the OGPX/VWRAP design. I certainly don&#39;t read it as &quot;We should

etc.

while the post that I send from gmail looks like this:

<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Just played with the new &quot;sit here&quot; pie menu and found a small hole in the logic.


As you see, you CLOSE the </blockquote> before the quote even starts. I think that is the problem.

-- 
Carlo Wood <carlo@alinoe.com>