Stream: committers
Topic: CommonMark support
Grahame Grieve (Jun 21 2017 at 04:03):
One of my todo items has been to add CommonMark support to the IG Publisher. I've just discovered that this won't be so easy: the IG Publisher processes the markdown from the spec. So to process common mark, I have to know on a per-markdown basis which dialect is in use
Grahame Grieve (Jun 21 2017 at 04:03):
not sure what I should do about that
Eric Haas (Jun 21 2017 at 16:30):
I use the kramdown variant for the Jekyll pages. I am asuming you mean that CommonMark Is for the generated fragments? Also is CommonMark implemented in the build now? ( i.e. can I make lists in the descriptions )
Grahame Grieve (Jun 21 2017 at 18:47):
no, it's not implemented in the build. And I think the only way I can implement it is to replace the existing dialect
Eric Haas (Jun 21 2017 at 18:48):
RE the IG -build it would only apply to generating the fragments right?
Eric Haas (Jun 21 2017 at 18:49):
in other words, Jekyll would still use Kramdown
Grahame Grieve (Jun 21 2017 at 18:49):
don't know. changing that would be changing it at Jekyll level - I don't know if that's possible, or if it would be good
Eric Haas (Jun 21 2017 at 18:52):
FWIW I use Kramdown markup everywhere in my igs
Last updated: Apr 12 2022 at 19:14 UTC
