Closed MasterOdin closed 3 years ago
Now that the AsciiDoc Language project is underway using AsciiDoc as defined by Asciidoctor as the starting point, I'm not going to sprinkle differences between AsciiDoc.py and Asciidoctor throughout this docs site any longer. Instead, that information should be relegated to the following migration page: https://docs.asciidoctor.org/asciidoctor/latest/migrate/asciidoc-py/ Feel free to submit a change to that page to call attention to it.
asciidoc-py does not support explicit ids and attempting to use them causes errors on parsing. For example, given the following file:
gives the following when attempted to be translated by asciidoc-py:
and the resulting file does not have the second header at all. Asciidoctor handles this as documented, with the second header appearing and with an explicitly set id.