This might be more useful if it also supported meta_creation-date: headers of the blosxom posts. When I started using Typo, I made a Perl converter that converted the stuff to RSS format. I'll attach it to that to serve as an inspiration as soon as I censor the profanities that I unavoidably added when I was trying to make sense of the date formats one last time. =)

I'm not sure what you mean by the meta_creation-date headers, since I switched to atom feeds in blosxom, but the converter actually works on the directory structure itself, not a feed. AFAIK the dates you get this way (mtime) are the same as what you see in blosxom.

Eh, what I meant was that my awful script, attached above, was used to convert my Blosxom contents to RSS2, which was then processed by Typo's RSS2 importer. Sorry for any confusion.

And my script reads the meta_creation-date headers as well as the mtime headers. If the proper Blosxom plugin is installed, Blosxom heeds the creation date header instead of the mtime, which makes it much more safe to edit the articles later on as the actual creation date is stored in the file, not in the fickle file mdates. The script attempted to use the creation date header as the "create" time and the mtime as the "last modified" time.

So I propose the Ruby-based importer would actually read both the meta_creation-date (if it exists) as well as mtime; if m_c-d exists, it would use that as the creation time and mtime as the last-modified time, if not, it would use mtime for both dates.

Ah, I see. I never knew of this meta_creation-date header (or any other header, unless you count the title) in blosxom posts. This is one of the difficulties with blosxom, everything depends heavily on which plugins you're using.