libasciidoc icon indicating copy to clipboard operation
libasciidoc copied to clipboard

A Golang library for processing Asciidoc files.

Results 61 libasciidoc issues
Sort by recently updated
recently updated
newest added

While working on #721 I noticed that the handling for callout lists is a bit dodgy, and differs in some ways from asciidoctor -- in particular the use of CSS...

type/feature
area/renderer

allow for `(parser/renderer)` scopes in the changelog also, include a section for the `refactoring` changes.

area/project
type/chore

A lot of what makes AsciiDoc so powerful is the variety of plugins available for it. I propose adding a simple plugin framework where golang plugins export functions that are...

The `format` attribute is meant to support custom data formats, like CSV, DSV, TSV, etc. Fixing this will require reworking the parser to support contextual parsing of the table contents.

type/feature
area/renderer

comma-separated attributes -> logical OR plus-separated attributes -> logical AND eg: ``` ifdef::backend-html5,backend-docbook5[Only shown when converting to HTML5 or DocBook 5.] ifdef::env-github+backend-html5[Only shown when converting to HTML5 on GitHub.] ```

type/feature
area/parser

I am working on a custom backend, mostly a copy of the xhtml5 one. For code content I need to wrap the content in CDATA blocks so I need the...

Libasciidoc does not provide a CSS yet, so by default there is no style in the document. The current workaround is to use the `-css` command-line flag. So what's missing...

type/feature
area/renderer

The video:: and audio:: elements are not supported. I suspect they are infrequently used, but the video ones especially may be useful for blogs and other content directed principally at...

type/feature
area/parser
area/renderer
area/types

What is this telling me? Where should I look in the .adoc file to figure out what to fix? `Error: unable to render full document: failed to render document elements:...

https://asciidoctor.org/docs/user-manual/#man-pages A subset is sufficient to document almost everything: bold, italics, links, section headers, definition lists, literal blocks. Apparently relates to #581. [scdoc](https://git.sr.ht/~sircmpwn/scdoc) is a good and brief resource--targeting the...