-
It would be great if readme_renderer supported [AsciiDoc](https://asciidoc.org/) natively. It has some very neat features and it would be nice to use the same format for our README as well as for the …
-
The project currently makes use of both Markdown (4 files) and Asciidoc (22 files) for documentation. For consistency, documentation should be aligned on either format.
-
**Is your feature request related to a problem? Please describe.**
I'm writing a book and the publisher requires that I use Asciidoc. I'd like to use this extension to check my grammar.
**Descri…
danvk updated
2 months ago
-
We use some asciidoc in the repo, let's get rid of it
-
### Description
Wrt configuring data sources for the Logs app, the UI says: "These settings only apply to the legacy Logs Stream app, and we do not recommend configuring them. Instead, use Logs Explo…
-
Currently, the output formats include asciidoc, fo, html, and text (`de.undercouch.citeproc.CSL#setOutputFormat(java.lang.String)`. Markdown is missing.
Some users do want to have Markdown (https:/…
-
Why? Because Madoko is no longer maintained as of 2019, and at least the P4 Language Design work group is considering switching from Madoko to AsciiDoc because of this. While the current Madoko sour…
-
With boost library documentation there are two factors that are both important:
- that the library docs can be built for any individual library, relatively conveniently, simply, directly.
- that the…
-
The HTML files for the various extensions currently in the repository were generated with various versions of asciidoc or asciidoctor and we do not currently check that the HTML files in the repositor…
-
### ⚠️ This issue respects the following points: ⚠️
- [X] This is a **enhancement/feature request**. Not a [bug or question](https://github.com/gsantner/markor/issues/new/choose).
- [X] The topic is …
Pyblo updated
4 months ago