NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Re: (Score:1)
I have two complaints with most mailinglist archives:
Lacking i18n.
I send mail as UTF-8, because I like to be able to use better typography than straight quotes and such, I like being able to use real bullet points, I like being able to mix Greek and Latin characters freely, etc.
But most archivers either simply assume my mail is Latin1, or just obliviously deliver their pages as Latin1 without ever bothering to transcode/escape their input properly. The result is that on the web, my mails appear full of garbage – ironically, browsers in general have much better Unicode support than mailers.
Sigh.
Almost no archivers show you the
Message-IDheader of a message. This means when you’re perusing the archives before you subscribe to the list, and you want to reply to something, there’s no way to thread things properly because you can’t find out the message ID of what you’re replying to.It would also be nice if there was a way to link to messages by their ID.
Reply to This
Re: (Score:2)
Regarding Message-Id display, I could add that quite easily by tweaking the stylesheet.
Re: (Score:1)
Great to know that you care. :-) You are exactly right, doing things correctly isn’t trivial but no rocket science either – just takes care and some effort. I only recently saw another list archive get encodings right for the first time, and then another, so I’m hopeful for this class of application.
I get discouraged sometimes by how many really, really basic things (i18n being just one of them) still don’t work right in so much software. We’re building castles on sand, it oc