I haven't been able to figure out how to specify the relative width of the columns in a org-mode table. Below is an idea of what I would like the asciidoc output to be, and I don't know how to achieve it.

[cols="1,1,3", options="header"]
|===
|Version
|Date
|Comment

|0.1
|2016-03-16
|Revisions after feedback from users.

First of all, thanks for this very gorgeous package, it really takes my ebook publishing workflow to the next level.

One thing that I might be missing (asciidoc beginner here!) is image support.

I guess the gist of the problem is that in org-mode an image is only

a link to an image file

(https://orgmode.org/manual/Images.html)

It does seem like it should be possible to filter out image links by looking at "image-file-name-extensions and image-file-name-regexps" (ibid.). Do you think it'd be possible to implement this?

When I export this file, the source blocks are exported as plain-text instead of asciidoc code blocks.

If I have a file with this in it:

: Test

The result is this:

: Test

I would expect to see something like this:

....
Test
....

I run into this a lot when executing source blocks where the result is output as:

#+RESULTS:
: Test

Asciidoc differentiates Listing Blocks (----) and Literal Blocks (....), however the current ox-asciidoc converts all three elements (src block, example block, fixed width) to the Listing Block. It'd be better to converts example blocks and fixed widths to the Literal Blocks (....), but keep src blocks to the Listing Blocks (----).

ox-html converts all three to pre, but classifies example blocks and colons to example, src blocks to src

I just think this might look nice.

Just copypasta this into readme.org.

[[https://melpa.org/#/ox-asciidoc][file:https://melpa.org/packages/ox-asciidoc-badge.svg]]

It would be nice if this:

#+CAPTION: My Sidebar
#+BEGIN_EXAMPLE
This is a sidebar.
#+END_EXAMPLE

Produced this:

.My Sidebar
****
This is a sidebar.
****

I think the difficult part is determining when an example block should be a literal block (....) or a sidebar. I guess if it's an example block AND it has a caption, it should be turned into a sidebar?

I get this error after using org-asciidoc-export-as-asciidoc

Looking for the element causing it found it's the unordered lists:

• element 1

The parser get's stuck there.

Thanks!

Hi! I just discovered this ORG exporter and I realized that not everything is exported properly into proper asciidoctor syntax.

Especially literals seem not to be exported properly. For example I'd like to have the ORG mode equivalent of this asciidoctor literal

[chart,pie,order=null,legend=right]
....
Code Review,27
Unit Testing,19
Functional Testing,13
Continuous Integration,12
Integration Testing,9
Detailed Requirements,7
Static Analysis,3
Training/On-boarding,3
User Stories,2
Other,5
....

Another one:

[plantuml, rma-sequence-diagram, svg]
....
participant User
User -> A: DoWork
activate A
A -> B: << createRequest >>
activate B
B -> C: DoWork
activate C
C --> B: WorkDone
destroy C
B --> A: RequestCreated
deactivate B
A -> User: Done
deactivate A
....

Is this supported at all? And if yes, what would be the ORG equivalent to the literals above?

Thanks in advance.

Runtime Environment

• MX Linux 17
• GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
  of 2018-11-28
• Evil version 1.2.13
• Org mode version 9.1.9
• .emacs.d
• packages
• ox-asciidoc-20171111.1154

Issue

The following Org syntax (as in the documentation):

- Name :: definition

Gives the following results on the exported file:

nil definition

When it should be:

Name :: definition

I'm using org-export-dispatch.

I'm receiving this error in org 8.3.1 with the version in elpa:
apply: Wrong type argument: listp, #("2014-07-31" 0 10 (:parent (#0)))

The file I'm attempting to export is here: https://raw.githubusercontent.com/kat-co/kat-co.github.io/source/blog/an-argument-for-parameter-validation.org

Another thing I just noticed is that quote blocks, i.e.

#+begin_quote
Some wise saying
#+end_quote

end up unconverted in the asciidoc, although there seems to be an asciidoc specification for blockquotes? https://docs.asciidoctor.org/asciidoc/latest/blocks/blockquotes/

Runtime Environment

• MX Linux 17
• GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
  of 2018-11-28
• Evil version 1.2.13
• Org mode version 9.1.9
• .emacs.d
• packages
• ox-asciidoc-20171111.1154

Issue

The following Org syntax:

/Some Empahized Text/

Is not exported as emphasis. It does this instead:

'Some Empahized Text'

When it should be:

_Some Empahized Text_

I'm using org-export-dispatch.

See: http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/#lists

* Every list item has at least one paragraph of content,
  which may be wrapped, even using a hanging indent.
+
Additional paragraphs or blocks are adjoined by putting
a list continuation on a line adjacent to both blocks.
+
list continuation:: a plus sign (`{plus}`) on a line by itself

* A literal paragraph does not require a list continuation.

 $ gem install asciidoctor

* AsciiDoc lists may contain any complex content.
+
[cols="2", options="header"]
|===
|Application
|Language

|AsciiDoc
|Python

|Asciidoctor
|Ruby
|===

In org, if I have this:

Continuation list:
1. Item 1
   With adjoining paragraph.
2. Item 2
   Also with adjoining paragraph.
3. Item 3
   Yep. Another adjoining paragraph.

I get this:

Continuation list:

. Item 1
With adjoining paragraph.
. Item 2
Also with adjoining paragraph.
. Item 3
Yep. Another adjoining paragraph.

And I would expect this:

Continuation list:

. Item 1
+
With adjoining paragraph.

. Item 2
+
Also with adjoining paragraph.

. Item 3
+
Yep. Another adjoining paragraph.

I think this is more of a question. If I use footnotes as described here, and have the following:

* My Text
  This sentence needs a footnote[fn:1].

* Footnotes
  [fn:1] http://www.google.com

How should that be translated into ASCIIdoc? This seems to suggest it should produce the following:

== My Text ==
This sentence needs a footnote footnoteref:[1]

== Footnotes ==
footnoteref:[1,http://www.google.com]