Sam Ruby wrote:
The highest priority is to make sure that the encoding is correct.  As
it currently stands, many of these feeds are not well formed XML,
meaning that they will be rejected by conformant XML parsers.  Fixing
this will improve the usability of the HTML pages.

An outline of what needs to be done can be found here:

  http://intertwingly.net/stories/2005/09/28/xchar.rb

This is in Ruby.  I can translate to C any portions you may have
questions on.

Well, this is actually a small part of the whole encoding problem.

Right now mod_mbox does *no* encoding translation. We really need to be calling apr_xlate all over, and turning everything into UTF-8 First. Currently, each item is encoded in whatever the client program sent it as... which isn't good.

There also is a minor issue regarding canonicalization.  Also, email
addresses should be split out from the name (I'll go fix the
feedvalidator to issue warnings on this).

Yep, I saw that part of the spec, but I was just being lazy when I wrote the atom stuff.

Reply via email to