On Thu, 17 Jan 2013, Dan Allen 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.
It hurts to say this, but I prefer GitHub dropped AsciiDoc support if they
cannot support it properly. I am a big fan of using AsciiDoc for
documentation, but my Github README in asciidoc never worked properly.
There was the problem that listing blocks did not retain newlines, so all
my examples were broken. And now it isn't even readable:
https://github.com/dagwieers/unoconv
If anyone was using the AsciiDoc functionality, keeping it broken for so
long (and now it doesn't even work), this is killing AsciiDoc in a crueler
way than if it wasn't supported. Anyone making the decision to go with
AsciiDoc is being punished and cannot even fix it (many bugs have been
unanswered for too long).
--
-- dag wieers, [email protected], http://dag.wieers.com/
-- dagit linux solutions, [email protected], http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
--
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.
