Jason McBrayer writes: > It is perhaps unfortunate that despite there being Markdown parser > libraries for every common language, practically all of them are > focused on generating HTML rather than generating (e.g.) a parse tree > that you could use in your own layout engine. I've actually looked at the internals of the Python and Common Lisp libraries for MarkDown, and they both have extension points that could reasonably be hijacked for returning parse trees, for what it's worth. Still might be a bit much for someone trying to write a quick-and-dirty client. -- +----------------------------------------------------------------------+ | Jason F. McBrayer jmcbray at carcosa.net | | The scalloped tatters of the King in Yellow must hide Yhtill forever.|
---
Previous in thread (9 of 148): 🗣️ Jason McBrayer (jmcbray (a) carcosa.net)
Next in thread (11 of 148): 🗣️ Jason McBrayer (jmcbray (a) carcosa.net)