All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

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

This does full i18n and it does it right even when the mailer gets it wrong. This isn't easy, but it's not rocket science either. Of course using AxKit and XML helps with this as it tends to make sure you get encoding just right or it falls flat.

Regarding Message-Id display, I could add that quite easily by tweaking the stylesheet.

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

: 1. What is the possibility of this being added in the future?
In the near future, the probability is close to zero. In the distant
future, I'll be dead, and posterity can do whatever they like... :-) --lwall

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.