-
Some of the macros we define for our user manual don't work with the current version of Asciidoc.
-
Update the documentation and the readme file is done manually by a human and this is error prone.
We already have a rake task that take care of updating the version of the gems and also the dependenc…
-
Is there a `preserveTOC` option for `rst` (as is for `asciidoc`)?
If not, would it be worth to implement it?
bzgec updated
4 months ago
-
[Enter steps to reproduce:]
1. installed panocia
2. ran panocia from Atom on a ".docx" file in buffer
3. convert failed
**Atom**: 1.45.0 x64
**Electron**: 4.2.7
**OS**: Microsoft Windows 10 …
-
Human: Expert Java dev, Ruby noobie
OS: Mac OS X 10.8.4
Ruby: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.4.0]
RVM: rvm 1.21.8 (stable)
Tried to follow instructions at http://asci…
-
The documentation is really sparse when it comes to describe the functionality for updating existing pages instead of just writing new ones. Can someone enlighten me how I can achieve this?
larsw updated
3 months ago
-
**Is your feature request related to a problem? Please describe.**
As a user of OpenSCD I need clear and accessible documentation.
Our current documentation while bundled within the app is not eas…
-
We have started using asciidoc rather than markdown for website content and documentation.
Right now chrisproject.org uses jekyll, which is markdown first although we have an asciidoc plugin for it…
-
Prior to the unification of the OpenCL specifications, the specification for many extensions stated the version of OpenCL required by the extension. The new extension appendix no longer seems to have …
-
## Description
So far the docs assumed that the user was more or less familiar with IntelliJ. Still there are people you want to try out IntelliJ just to try out how working with AsciiDoc feels lik…