Return-Path: 
 <general-return-9517-apmail-incubator-general-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-general-archive@www.apache.org
Received: (qmail 58704 invoked from network); 3 Jul 2006 15:19:26 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 3 Jul 2006 15:19:26 -0000
Received: (qmail 81731 invoked by uid 500); 3 Jul 2006 15:19:20 -0000
Delivered-To: apmail-incubator-general-archive@incubator.apache.org
Received: (qmail 81586 invoked by uid 500); 3 Jul 2006 15:19:19 -0000
Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:general-help@incubator.apache.org>
List-Unsubscribe: <mailto:general-unsubscribe@incubator.apache.org>
List-Post: <mailto:general@incubator.apache.org>
List-Id: <general.incubator.apache.org>
Reply-To: general@incubator.apache.org
Delivered-To: mailing list general@incubator.apache.org
Received: (qmail 81563 invoked by uid 99); 3 Jul 2006 15:19:18 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Jul 2006 08:19:18 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of chip@force-elite.com designates
 216.255.199.145 as permitted sender)
Received: from [216.255.199.145] (HELO utopia.in.force-elite.com)
 (216.255.199.145)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Jul 2006 08:19:18 -0700
X-AuthUser: chip@force-elite.com
Received: from [127.0.0.1] (127.0.0.1:53626)
	by localhost with [XMail 1.17 (Linux/Ix86) ESMTP Server]
	id <S10B180> for <general@incubator.apache.org> from <chip@force-elite.com>;
	Mon, 03 Jul 2006 08:18:55 -0700
Message-ID: <44A9355E.9040903@force-elite.com>
Date: Mon, 03 Jul 2006 08:18:54 -0700
From: Paul Querna <chip@force-elite.com>
User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060426)
MIME-Version: 1.0
To: general@incubator.apache.org,  dev@httpd.apache.org
Subject: Re: atom feeds for projects
References: <f470f68e0607021356m50c68086rd8b8eb13dce3b680@mail.gmail.com>
	 <44A845DF.4030509@apache.org>
 <f470f68e0607030430k26e5031aqe80e58c7ea0a3323@mail.gmail.com>
In-Reply-To: <f470f68e0607030430k26e5031aqe80e58c7ea0a3323@mail.gmail.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

robert burrell donkin wrote:
> On 7/2/06, Sam Ruby <rubys@apache.org> wrote:
>>
>> robert burrell donkin wrote:
>> > the mailing list archives at apache run on mod_mbox which also supplies
>> > atom
>> > feeds for these lists. i've added the feed from general to the front
>> page
>> > and think it'd be cool to add feeds to the pages in projects as well.
>> since
>> > the focus of  podlings should be recruiting developers (not users) i'm
>> > thinking of adding feeds to the dev lists.
>> >
>> > opinions?
>> >
>> > volunteers?
>>
>> Just be aware that the feeds produced are rarely well formed XML, mostly
>> due to encoding issues.  For example: http://tinyurl.com/h5f7t
>>
>> I tried to submit a patch based on my limited understanding of the code,
>> and was told that my patch wasn't acceptable

To be clear, AFAIK, there was never a patch for mod_mbox -- it was a
Ruby file that only solved part of the problem. Again, AFAIK, no one
ever wrote a patch in C for mod_mbox to attempt to resolve this issue.

>> and that XML parsers that
>> require well-formedness were broken anyway -- despite that being
>> explicitly what the spec requires.

Its unfortunate that the discussion degraded into that.

>> I'd be willing to try again, but only if there was active interest in
>> actually fixing the problem.

Yes, there is active interest in making mod_box better.

> IMO we should fix the feed but i'm not involved with mod_mbox (or httpd).
> anyone who is want to jump in here?

The primary bug is lack of encoding support.  mod-mbox just doesn't even
try to do it.

Someone needs to write something that touches many parts of the code,
using the apr_xlate API to convert the content to utf-8.  (This would
also help it validate as HTML).  Once that is done, we do need to worry
about out of range characters, some of which would be removed, others
possibly HTML encoded.

For future discussion of this please use dev@httpd.

Thanks,

-Paul


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org