in reply to Re^3: Markdown syntax useful to the Monestary?
in thread Markdown syntax useful to the Monastery?
It's probably a naive view by someone that hasn't witnessed the range of errors that you guys correct, but it seems to me that something like markdown ought to reduce your workload.
If the conversion filter is any good, it will fail to allow commitment of a post that fails to produce acceptable html from it's markup and prompt the user to correct it before it will perform the conversion.
The way I envisage it working is that once the filter accepts the markup, it sends the html back to the user and discards the markdown. The user then has to preview the html in raw and formatted states (as now) before submitting, giving them the chance to amend the html if desired. They could also hit the back button to return to the markdown version and tweak it further, before again attempting the conversion.
In this way, the only markup stored is the html, the markdown would simply be an intermediate shortcut to arriving at acceptable html. And if that html is produced by a filter, it ought to be free of errors. If the user modifies the html, there is the possibility that they will screw it up, but that's no different to now, accept that they would be starting from an acceptable starting point without missing end tags or (PM) illegal tags.
The same thing could be achieved by using an offline conversion I suppose, which would have the advantage of allowing a proper editor to be used instead of the editbox I'm currently typing in. The problem with that is either everyone has to produce their own filter/editor/submit/verify/re-edit script, with the consequent mish-mash of complience with site html standards. Or, someone produces a standard module for doing it and tries to make it general enough to work with the 1000 varieties of preferred editor.
It's far from a big thing, just a convenience, if it is possible, and it doesn't impact the servers too much.