Colin Bartolome

Would it be possible for the spec to indicate both the expected AST and the reference rendering of the expected HTML? Implementations could then target either AST compliance or exact...

Could the translation from TXT to HTML leave out the AST? Or maybe give each bit of expected AST and HTML certain CSS classes, hide the AST, then add a...

This project shows off the issue much more succinctly: https://github.com/CPColin/issue-1894

This also makes it tough to run `tagged` tests.

I ran into this a month ago and reported it here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=466003#c3 Things worked fine once I deleted version 4.5.2 of `httpclient` and version 4.4.6 of `httpcore`.

Try deleting `org.apache.httpcomponents.httpclient_4.5.2.v20170210-0925.jar` and `org.apache.httpcomponents.httpcore_4.4.6.v20170210-0925.jar`.

Is the `actual` parameter supposed to come first in `assertEquals`?

> See [the test module docs](https://modules.ceylon-lang.org/repo/1/ceylon/test/1.3.3.1/module-doc/api/index.html#assertEquals), so, yes. Some of your tests have the `expected` value first, instead of the `actual` value.

I went back to the drawing board on this and did a direct port from `commonmark.js`: https://github.com/CPColin/ceylon.markdown I'm not sure if we can use this as a starting point for...

It's a rhetorical device to soften the impact of my going back to the drawing board, instead of continuing Rohit's work (and borrowing the strategy of fetching the spec tests...