I have a need to convert markdown into something other then html. To that end it made sense to convert an existing implementation to support that. This change does a few things.
The goal I have here is to provide a reasonably complete set of matches. Let me know if something different needs to be done.
make the version number in the app metadata and the README match
rename the internal parse to 'to_html'
This disambiguates the parsing of text to tagged tuples from the
conversion of tagged tuples to html.
expose a 'parse' function that allows callers to get the intermidate …
Happy to pull it.
We no longer use erlmarkdown in production so if you want to fork it and integrate it into any of your suite of libraries I am happy to deprecate my version and push people to use yours.
So, let me know, pull or fork, and I will make it so.
I need it for a couple of projects so we can accept that. Give me a couple of days to do some refactoring and get it setup in erlware and we can make the transition. I will send you a message when we are ready.
We cut out the email validation stuff and used it elsewhere at Hypernumbers. I found a bug in it so I have pushed a fix for that too.
Basically it would reject Gordon@hypernumbers.com as an invalid e-mail addie cos it only recognised lower case :(
I have forked this to erlware/erlmarkdown. We can use that as the canonical repo and start directing folks there.
Cheers Eric, done and over here.