A script file is found with a name that matches the filter folder, and the script ends in any of “php”, “pl”, “py”, “rb”, or “sh”.

I don’t see any reason to restrict it to these so I’ll be changing it to accept any script starting with the name of the filter folder. In the longer term I still like your idea of using an Info.plist.

Other windows apps that are worth looking at are Windows Live Writer and BlogJet.

I don’t know much about Windows software, but ecto might do the trick?

Thanks a lot, Daniel. Nothing but love for MarsEdit, it’s great.

The fact that users can create their own filters is under-publicized. I’d love for more people to know about this option, so I am especially happy that you wrote about it.

It must be a side-effect of this relative lack of recognition, that there are some quirks remaining to be ironed out. I didn’t realize the limitations you mentioned about its perl assumptions.

I want to point out that the system is currently more functional than you know, but it does have an obvious failing with led you to the conclusion that it only supports perl filters. In fact, it looks like it requires the text filter script to be the name of the filter, plus the extension “.pl”. That would make any reasonable person assume it must be perl, but in fact the script can be any shebang-style script.

Try putting #!/usr/bin/php in the Whatever.pl script and you’ll see what I mean.

I’ll get this sorted out in an update. I like your idea to remove all guesswork and just put the full name of the appropriate script inside an Info.plist.

Daniel