On 18 January 2013 13:19, Dan Allen <[email protected]> wrote: > On Thu, Jan 17, 2013 at 5:47 PM, Lex Trotman <[email protected]> wrote: >> >> On 18 January 2013 11:32, Dan Allen <[email protected]> wrote: >> > Indeed. The new version has gotten the green light and, afaik, we are >> > waiting on a new deployment of that code to the production instance. Any >> > day >> > now. >> > >> > ...and it wasn't just an upgrade to a new version of AsciiDoc. It was a >> > switch to a new implementation of AsciiDoc, named Asciidoctor [1]. But >> > you >> > shouldn't notice the different as it's close to 100% compliant with >> > AsciiDoc >> > rendering. There are still a few outstanding issues, but it won't be >> > long >> > before we get them polished off. >> >> Like a specification for what markup works. > > > Yep. I've got a top-level post in the works on that topic. Will post soon.
Good, because if someone as significant as Github is going to use a half-assed implementation instead of the real one then it better be properly documented. Cheers Lex > > -Dan > > -- > Dan Allen > Principal Software Engineer, Red Hat | Author of Seam in Action > Registered Linux User #231597 > > http://google.com/profiles/dan.j.allen > http://mojavelinux.com > http://mojavelinux.com/seaminaction > > -- > You received this message because you are subscribed to the Google Groups > "asciidoc" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/asciidoc?hl=en. -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/asciidoc?hl=en.
