The repo contains a new file: ./tests/testa2x3.py You guessed it - it contains an easy approach to test (or to explore!) the power of a2x3.py. It shows very fast (using concurrent.futures) the potential of this probably underrated tool: producing god looking (x)html, pdf, text, dvi, ps, tex, manpages and epub. Take a look and find out!

Keywords: asciidoc3 a2x3.py tests

Two recent threads ask the question about the future development of AsciiDoc:
The first wonders »What is the maintainer’s vision for asciidoc-py?«, the second covers the »Asciidoc specification«. The postings are a little sceptical that the further development of AsciiDoc is assured. No decisive answer was given.
We can only speak for AsciiDoc3, of course. You may rest assured (to say it formally) that we keep on with working and developing AsciiDoc3 as a Python3 software package. Nothing more and nothing less.

Keywords: asciidoc3 asciidoc maintainer specification development

Found this issue about PyPI:

And our answer:
» Indeed the PyPI/pip installation as root does not work.«
That is a known amd intended behavior: because of the many conf-files you need to run asciidoc3_postinstall immediately after pip3 install. This makes only sense as a normal user (not root) with option --user:
normaluser$ pip3 install --user asciidoc3
For system wide installation (as root) we recommend to download the tarball asciidoc3-3.1.0.tar.gz
All information is found here: https://asciidoc3.org.

Keywords: asciidoc3 pypi pip root aix

Some people enquire about that: »How many downloads of AsciiDoc3 do you see on an average day?« Here’s the answer: At least 12. Why »at least«: We have no info from PyPI and many users »do not track«. Twelve is the amount monitored by asciidoc3.org. So, maybe, the correct answer is 22, or 34, or 42? Who knows?
We are proud to notice that our work is so much appreciated, thx.

Keywords: download rate asciidoc3

Hi everybody - here’s a second update regarding the roadmap towards AsciiDoc3-3.1.1. In the previous post I wrote about a bug when using a2x3 with option --dry-run. This behaviour is only seen when the output is chosen as -f epub. And, this bug also comes to pass in AsciiDoc 8.6.9 (Python 2.x)! It seems that nobody - me too - has noticed this issue for more than ten years …
Therefore I decided to exit the program with a warning and postpone the search for a fix for this dispensable (?) bug. So we can concentrate on the implementation of DocBook5.1.
Keywords: asciidoc3 a2x3 dry-run epub bug

Here comes an update for the raodmap towards AsciiDoc3-3.1.1. Support of DocBook5.1 will be included as announced in our previous post.
Argparse will replace the deprecated optparse in a2x3.py - getopt (which is not deprecated) will remain in asciidoc3.py.
During our work on these enhancements we encountered one minor bug in a2x3.py when using option --dry-run. So everything takes up a little more time to implement, please be patient: AsciiDoc3-3.1.1 comes in the first ten days of Aug-19.

Keywords: asciidoc3 docbook5 argparse a2x3

The next version AsciiDoc3-3.1.1 is scheduled for July 19. There will be included one bigger feature for you: (full) support of DocBook5.1! You may choose your backend between well known DocBook4.5 and the up-to-date DocBook5.1 rewritten with RelaxNG. AsciiDoc3 produces the xml-file and validates it.
We’ll see another modification: argparse replaces the deprecated optparse. And at last: a more secure and smart implementing of the installing scripts and new uninstalling scripts, too.

Keywords: asciidoc3 docbook5 argparse

A few bugs have been fixed with the latest release AsciiDoc3-3.1.0. One example: when executing a2x3 -f pdf --fop userguide.txt the output shows the title two times.
This occurs only when generating PDF with FOP, not dblatex. We have seen this behaviour under both GNU/Linux and Windows.
Double Titel
This was fixed - the reason was found in asciidoc3’s reading some conf-files two times.

Keywords: asciidoc3 a2x3 pdf fop title headline double bugfix

At last, AsciiDoc3 has reached another milestone!

Please, do not become desperate: asap there will be a PyPI distribution not only for GNU/Linux and POSIX, but for Windows, too!

At last, today the new AsciiDoc3-3.1.0 is out!

Asap: there will be a PyPI distribution not only for GNU/Linux and POSIX, but for Windows, too!

The next release AsciiDoc3-3.1.0 will be more than just a bugfix:

The biggest thing for the user: there will be a PyPI distribution not only for GNU/Linux and POSIX, but for Windows, too!
AsciiDoc3-3.1.0 is scheduled for the end of Feb '19.

When using another language than English you’ll may see in the footer of your HTML-output something like this

The Not-Ascii characters are not translated in a proper way. This bug pops up especially under MS-Windows. This is caused (in few words) by the template [footer-text] in the lang-*.conf (e.g. lang-de.conf) or the layout.conf.
We fixed this (hopefully), our tests showed satisfactory results. But perhaps we do not cover all languages and/or time zones … If so, leave us a note.
The tarball asciidoc3-3.0.3.tar.gz, https://asciidoc3.org/download.html, and the repo, https://gitlab.com/asciidoc3/asciidoc3, are updated.

Today the new AsciiDoc3-3.0.3 is out! It is about 15% faster than before.
And we have fixed some bugs: the following message

is gone away . . .