Re: [ogpx] Cable Beach + VWRAP update

[Morgaine <[e-mail]>]

Well it's just Gmail, I guess it's buggy if you say it produces broken
HTML.  But notice that it's NOT broken on the IETF mailman site.  The
indentation is preserved perfectly, even when a quoted mail body is
split into sections for interleaving responses.


Morgaine.




========================================

On Wed, Jan 20, 2010 at 2:50 PM, Carlo Wood <[e-mail]> wrote:
> On Wed, Jan 20, 2010 at 12:27:00AM +0000, Morgaine wrote:
>> On Tue, Jan 19, 2010 at 1:11 PM, Carlo Wood <[e-mail]> 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 <[e-mail]>
>