xmllint shouldn't touch it if it's in CDATA tags. Which it's not, but that can be easily configured in AsciiDoc. But I'm noticing that xmllint is smart enough to recognize the docbook schema and is not reflowing programlisting blocks. Interesting.

AsciiDoc has not yet ceased to amaze me. The entire processing is done via a configuration pipeline, so you could make AsciiDoc behave like reStructuredText or Markdown if you really wanted to. That's great for use as a templating engine (think Awestruct) because you can tweak how it creates the HTML it creates. With Textile (RedCloth) you would have to modify generated Java code and recompile the whole gem. Not nearly as convenient

The only big downside I see to AsciiDoc (if you held my hand to the fire to come up with something), it's that the code itself is not modularized. Instead, it's two very large python scripts. That's why my hope is that in the long run, someone reimplements the same pipeline in a very clean and modular way. I have hopes for this Ruby project, but it's still early.

...I would also like to see AsciiDoc make less use of commandline tools. I like the idea that it supports plugging in a commandline tool at any stage in the process....that's good for people building on it, but I would hope that in the long run it can bundle all this up to be self-contained (for the core functionality).

My current understanding is that we plan to use Markdown for things like READMES (I'm against changing this, we've got a lot of investment in using Markdown here now), and something like Ascidoc for longer documentation. We'll then generate HTML from it, which can be embedded into JBoss.org pages as needed.

...I would also like to see AsciiDoc make less use of commandline tools. I like the idea that it supports plugging in a commandline tool at any stage in the process....that's good for people building on it, but I would hope that in the long run it can bundle all this up to be self-contained (for the core functionality).

Sounds like a rewrite is needed. One of the things I loved about docutils (at the code level) is that it's very modular and it creates an intermediate representation of the file so it becomes easy to create other outputs. I don't like how it can't be extended save by other declarations, you can't add syntax. A more modular structure to ASCIIDOC may allow this and make it easier to use / extend. Probably won't happen though unless we fork it.

Call it a refactoring AsciiDoc does write temporary files in some cases. But not really for the same reason that docutils does.

There are really two options. The more lightweight approach is helping flesh out the Ruby port, since that has a good foundation for modularity already. What it's missing so far is block-level templating (it only supports templating at the line and char level). If it had that, things would progress quickly. I'll file an issue just to get the ball rolling.

It looks like someone has put together an API wrapper for AsciiDoc for support in the Github markup engine. That simplifies integration with Python and would likely make it easier to use the JSR-233 APIs (except there is still that bug with script size).

I wonder if AsciiDoc would consider accepting this API wrapper into the mainline? I suppose we could submit it upstream. First, I want to play around with it.

I'm definitely an asciidoc fan. It has a great potential. Even its support for graphical contents like plantuml/ditaa is great.

Dan Allen ha scritto:

Dan Allen ha scritto:

But that's just one pipeline. Since AsciiDoc is remarkably portable and readable, we can easily reuse it in many other areas. We can paste it into a gist, paste it into a github wiki page, paste it into a blog entry, paste it on Google+, and so on.

a web frontend intended to display an AsciiDoc documentation repository. It allows to search and browse your documentation files and automatically converts AsciiDoc to HTML, PDF and ODF documents. It is intended to work directly from a subversion repository containing your AsciiDoc files.

but I've not been able to give it a test. You could be interested, and maybe it could resurrect...