#5

Yes I would LOVE! to see AsciiDoc support at some stage.

I was a huge fan of markdown 10 years ago and managed to convince a lot of people to adopt it at the time, however the more you use it the more you come across shortcomings (which have been resolved to a certain extent in various different “flavours” of markdown.)

To me that is the single biggest issue with markdown… CommonMark never really took off and there are too many different implementations floating around in the inter webs. None of them resolve all the shortcomings in a consistent manner.

The best and simplest solution is AsciiDoctor. It is really well documented and well thought through. It takes about 30 mins to learn all the basic syntax and you can rest assured that all the complicated corner cases have been properly and consistently addressed, such as:

  • Embedding multiple other asciidoc files into a master doc
  • Specifying the image size and text flow
  • Writing complete books with it
  • Foonotes
  • References
  • etc… (all these things are handled very elegantly)

I would not care about having a preview option in asciidoc (even though it should be straight forward enough with asciidoctor.js).

@Silver You could easily capture a large portion of the asciidoc users with Obsidian.

8 Likes
#6

While I too would like asciidoct support, there are other things on my list at a higher priority and I suspect this is not even on the developers’ list!

But you can convert asciidoc to git format markdown etc. going via a docbook format intermediate step. Something like

asciidoctor -b docbook -a leveloffset=+1 -o - foo.adoc | \
pandoc --atx-headers --wrap=preserve -t gfm -f docbook - > foo.md

The conversion is not perfect but good enough.

#7

I wish to revive this topic. I would really love asciidoc support. What can I do to advocate for it?

1 Like
#8

Hey this thread is not even labelled as feature request. OP?

1 Like
#9

Is it possible to change? If not, I am happy to own the thread and champion this!

#10

Quick update, I spoke to some of the folks at my work and we’re interested in a corporate license for the team if we had alternative formats, specifically AsciiDoc. What can we do to jump-start or otherwise ignite this discussion?

#11

I would also prefer to use Asciidoc instead of markdown. For all the basics, Asciidoctor supports writing it using exactly the same syntax as markdown (so for simple documents they are the same), but it’s got lots of extra features built in:

  • Simpler & better tables
  • Frontmatter
  • TOC’s
  • Inter-document linking

etc…

5 Likes
#12

I also want to donate to support AsciiDoc. Obsidian on AsciiDoc seems to me an uncompromising and perfect space. Asciidoc has includes, variables, and basic if…there.

1 Like
#13

+1 for Asciidoc support

1 Like
#14

+1 for asciidoc

2 Likes
#15

another vote for asciidoc from me

1 Like
#16

+1 for AsciiDoc from me

1 Like
#17

+1 for Asciidoc.

Shouldn’t this be under Feature Request?

1 Like
#18

:+1: Would be nice to have a preview mode for Asciidoctor PDF.

#19

+1 for Asciidoc support.

#20

+1 for asciidoc support too!

#21

+1 for Asciidoc support from me as well

#22

+1 on asciidoc

#23

+1 for Asciidoc support

#24

Why not reStructuredText?

It’s used by the Linux Kernel, has the same benefits as AsciiDoc but a much better syntactic and semantic foundation.

I think RST is the future due to how expressive, standardized (including the tooling) and well documented it is, but having all three major light markup languages (MD, AD and RST) would be ideal.

In any case, I agree that Markdown is just straight up bad.