1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues

Issues

Issue #7132 new

Render AsciiDoc files (BB-1913)

Dobrosław Żybort
created an issue

Hello,

would be nice if you could render AsciiDoc files (after all it's written in Python).

File extensions to catch:

.ad, .adoc and .asciidoc

(and probably .ad.txt, .adoc.txt and .asciidoc.txt: https://code.google.com/p/asciidoc/issues/detail?id=13 )

Repo with samples: https://bitbucket.org/matrixik/asciidoc-samples

Comments (67)

  1. Jochen Hinrichsen

    +1 While i like Markdown, Asciidoc outputs Docbook out of the box which opens up the whole nine yard of the publishing pipeline.

    As an implementation, i'd rather choose the newer Ruby based Asciidoctor instead of the older Python based Asciidoc.

  2. Dan Allen

    +1

    There's a Java API for Asciidoctor called AsciidoctorJ that encapsulates the use of JRuby. Bintray uses AsciidoctorJ to render AsciiDoc files. Asciidoctor runs fastest on JRuby anyway.

    Asciidoctor is also very secure for serve-rside usage. By default it runs in secure mode, which disables all file system access. You are free to enable the functionality from there that works best for you.

    AsciiDoc is gaining a lot of traction with big name authors lately, largely do to the innovation & advocacy coming out of the Asciidoctor project & community.

    GitHub uses Asciidoctor to render AsciiDoc, but it hasn't been upgraded past version 0.1.0 released in January. BitBucket could grab the reigns here by deploying 0.1.4 or 1.5.0.preview.1.

  3. zgamero

    I've tried reST, Markdown and AsciiDoc, finding the last one the more confortable and it's growing in popularity, IMHO.

    +1 for adding AsciiDoc

  4. Daniel Grigg

    +1 so colleagues will stop complaining about me writing bitbucket-un-renderable readme's

    Honestly asciidoc is just more feature-complete with less hacks required for writing technical docs.

  5. Arto Astala

    +1 Makes you wonder what use is issue tracker when a feature has issue filed, +1:d a lot, requested for readmes, is easy to implement and safe but sees no action or even comment from staff. Didn't even bother to change status from new in more than two years.

  6. Olga NA

    I'll leave my two cents here. Please consider reconsidering and adding asciidoc in the nearest future. If we could have it by new year 2016 =) Please?

  7. marco

    The only reason I am still using bitbucket is because I prefer hg to git. But I think asciidoc is so good that you are forcing me to go to github because you don't render asciidoc :-( As another poster already pointed out, the modern asciidoctor (not plain asciidoc) provides everything to render. I am saddened and I don't understand bitbucket's way of thinking, this seems a low-hanging fruit to make a lot of people happy :-/ And yes I saw the post about the addon. Why making it so complicated?

  8. Tobias Roeser

    +1 for AsciiDoc support, preferably the Asciidoctor version.

    Asciidoc(tor) is pretty standard nowaday for developers and many other platforms and tools support it, also GitHub and GitBucket.

  9. Jim Nasby

    It's really silly that BitBucket doesn't support this. AsciiDoctor (or even AsciiDoc) is far more powerful than markdown. You're really pushing people to github because of this.

  10. Jobin Jacob Kavalam

    AsciiDoc support please ... I recently moved onto AsciiDoc from Markdown as my preferred format for technical documentation and I have been quite pleased to find that AsciiDoc is more feature rich. Hence IMO it adds great value to support the format out of the box on Bitbucket. Otherwise, I just love Bitbucket !

  11. Log in to comment