On Wed, 2006-04-05 at 13:20 +0200, Øystein Gisnås wrote:
> tags 351087 moreinfo unreproducible
> stop
>
> > The in-reply-to and references headers are
> > getting the enclosing <>s hex-encoded.
>
> I'm not able to reproduce this.
I don't see the problem here either any more; I have
upgraded evolution several times since reporting the problem.
> Can you clarify? Is it for emails you
> send when you reply to a message,
yes.
> or when displaying incoming emails? If
> you provide an example message, it might be easier to reproduce..
I gave an example in the bug report:
In-Reply-To: [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
Content-Type: text/plain
Date: Wed, 25 Jan 2006 09:05:20 -0600
Message-Id: <[EMAIL PROTECTED]>
Mime-Version: 1.0
X-Mailer: Evolution 2.4.2.1
The full message is attached.
> Thanks
--
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
--- Begin Message ---
[...]
> http://www.w3.org/2001/sw/DataAccess/tests/data/simple2/dawg-tp-04.rq
[...]
> Is my interpretation of the grammar correct and should these tests be
> updated?
Yes.
Thanks for pointing out this problem with the test materials.
The spec itself is in last call, where the WG has a rather
formal obligation to address all comments.
We'll eventually get around to cleaning up the test materials...
the WG has been discussing it...
[[
those are the only ones (4 IIRC) I'm aware of that have become erroneous
due to syntax changes in the spec.
]]
-- http://lists.w3.org/Archives/Public/public-rdf-dawg/2006JanMar/0142.html
... meanwhile, I hope this is a satisfactory response regarding the
spec itself.
Please let us know whether it is.
If you're satisfied, you can put [closed] in the subject
of your reply to save us a bit of bookkeeping.
--
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541 0875 0F91 96DE 6E52 C29E
--- End Message ---
