MSIE is working now (for some non-zero value of "working")

If you're viewing this with Microsoft Internet Explorer, you're probably wondering what that "Content-type: HASH(0x3d743c)" line is doing up there.

Beats the crap out of me. I can't figure out where it's coming from. Neither can Jack. But at least the blog postings display correctly now.

As for how I got it to display at all, I hacked the Perl script engine to insert a CR LF combo in front of the script output if the browser is MSIE.

UPDATE 31 May 2007 11:21:
Geeky stuff for folks who care about how I got Blosxom correctly configured on VMS.

The head.html file needed a <!DOCTYPE> tag, and a meta tag with "content-type" set to "text/html". This is what fixed the MSIE display problems.

The other problem I had was getting plugins to work. Blosxom has an extensive library of useful Perl macros that enhance its functionality. The basic idea is you put the plugin code into a directory, and name the file "plugin" (no file extension). Blosxom reads this directory, and uses Unix "grep" magic to grab the file names. The problem is, VMS file names don't look like Unix file names, and VMS always puts a "." after the file name. So the Unix file /lib/blosxom/plugins/update becomes /lib/blosxom/plugins/update. on VMS. The Perl code which strips out the plugin name (update) was choking on the "." character. Ugh. So, I got rid of the grep code, thereby grabbing all the files in the /plugin directory (yes, I know it's a cheesy solution - it's my plugin directory and I can make sure that only plugins go in it). Then I put in some Perl code to strip the trailing "." from the file name.

Voila! The plugins work now. This update is brought to you by the "update" plugin.

Posted at 17:18 by Chris Wysocki   [/vms]   Comments | Perm Link |   |   Tweet