Thank you very much for your e-mail and please excuse my late response
-- regrettably, I was not paying much attention to my mailbox lately.
> (And... if BlazeBlogger only supported some non-HTML markup syntax (as
> an addition, not replacing HTML), preferably MoinMoin or MediaWiki, it
> would be just about perfect ;-).)
I am glad I can say that this has been already done in the latest
development version and will be included in the next release pretty
soon! :-) Support for another markup language was one of the features
I wanted there from the very beginning, but kept postponing it,
because I was not sure how to implement it best. I hope you will like
Since I wanted it to be as flexible as possible, I decided to
implement it in a form of another configuration option,
core.processor; if set, both blaze-add and blaze-edit let you edit the
raw file in whatever markup you choose and then call the processor to
convert it to HTML. The main advantages of this particular solution
are as follows:
1. blaze-make is not slowed down at all, because it works with
already converted files.
2. Old posts are not affected and you are still able to edit them in
the HTML directly.
3. You can choose whatever markup you want and not only that!
core.processor has many other uses: you can use it to replace your own
placeholders, validate/fix the input, add some automatic content like
contact form etc.
So, to write your posts in Markdown, all you have to do is type:
$ blaze-config core.processor 'markdown --html4tags %in% > %out%'
Similar approach applies to other markups.
> So... I would like to see a new feature that would, in addition to
> %root%, replace arbitrary %foo% with user-specified replacements. I've
> already hacked this into my own copy of blaze-make, so I can provide a
> patch, but I don't know what to do with it :-). Would this be a
> feature worth adding, and if so, where do I send the patch?
Once again, this is perfect candidate for core.processor option rather
than hacking it to the blaze-make, and can be easily done using sed or
awk. I really don't think that this is something that ought to be
implemented in core BlazeBlogger. As an external application, it can
be much more sophisticated: you can even make it replace ordinary text
smileys. Nevertheless, if you disagree, you can send me your patch
(either to my personal e-mail or add it as an issue to the bugtracker
on Google Code) and I will take a look at your solution.
Anyway, if you are interested and do not want to wait for official
release, you can find the latest development version (as well as not
yet announced bash completion and quick reference card ;-)) at
In case you decide to test it,
please, let me know what you think about it, user feedback is always