asciidoctor-diagram 2.2.10 → 2.2.12.next1

data/docs/modules/ROOT/pages/diagram_types/structurizr.adoc

@@ -1,29 +0,0 @@
-= Structurizr
-include::partial$uris.adoc[]
-
-{uri-structurizr}[Structurizr] builds upon "diagrams as code", allowing you to create multiple software architecture diagrams from a single model.
-There are a number of tools for creating Structurizr compatible workspaces, with the Structurizr DSL being the recommended option for most teams.
-
-The Structurizr extension allows individual views from a Structurizr DSL workspace to be included in Asciidoc documents.
-This is the inverse use case of https://structurizr.com/help/documentation[Structurizr's documentation] support which lets you embed Asciidoc in the Structurizr DSL.
-
-This extension uses the https://structurizr.com/help/cli[Structurizr CLI] tool to convert Structurizr DSL files into the input for a renderer.
-The chosen renderer is then used to generate the final image.
-
-The installation location of Structurizr CLI needs to be passed to asciidoctor-diagram using the `DIAGRAM_STRUCTURIZRCLI_HOME`.
-When running Asciidoctor with JRuby or when using AsciidoctorJ the installation location can also be specified using the `diagram.structurizrcli.home` Java system property.
-In both cases it should be set to the absolute directory containing the extracted Structurizr CLI archive.
-
-== Supported Image Formats
-
-- PNG
-- SVG
-
-== Attributes
-
-[cols=">,<,<",options="header"]
-|===
-|Name          |Default value   |Description
-|renderer      |plantuml-c4     |The rendering backend to use. One of `d2`, `graphviz`, `mermaid`, `plantuml`, or `plantuml-c4`
-|view          |unspecified     |The key of the view to render
-|===

data/docs/modules/ROOT/pages/diagram_types/svgbob.adoc

@@ -1,21 +0,0 @@
-= SvgBob
-include::partial$uris.adoc[]
-
-{uri-svgbob}[SvgBob] can create a nice graphical representation of your text diagrams.
-
-== Supported Image Formats
-
-- SVG
-- TXT
-
-== Attributes
-
-[cols=">,<,<",options="header"]
-|===
-|Name          |Default value   |Description
-|svgbob        |svgbob          |The path to the `svgbob` executable
-|font-family   |arial           |text will be rendered with this font
-|font-size     |14              |text will be rendered with this font size
-|scale         |1               |scale the entire svg (dimensions, font size, stroke width) by this factor
-|stroke-width  |2               |stroke width for all lines
-|===

data/docs/modules/ROOT/pages/diagram_types/symbolator.adoc

@@ -1,19 +0,0 @@
-= Symbolator
-include::partial$uris.adoc[]
-
-{uri-symbolator}[Symbolator] is a component diagramming tool for VHDL and Verilog.
-It will parse HDL source files, extract components or modules and render them as an image.
-
-== Supported Image Formats
-
-- PDF
-- PNG
-- SVG
-
-== Attributes
-
-[cols=">,<,<",options="header"]
-|===
-|Name          |Default value   |Description
-|symbolator    |symbolator      |The path to the `symbolator` executable
-|===

data/docs/modules/ROOT/pages/diagram_types/syntrax.adoc

@@ -1,28 +0,0 @@
-= Syntrax / JSyntrax
-include::partial$uris.adoc[]
-
-{uri-syntrax}[Syntrax] is a railroad diagram generator.
-It creates a visual illustration of the grammar used for programming languages.
-A specification file describes the syntax as a hierarchy of basic elements.
-This is processed into an image representing the same syntax with interconnected nodes.
-
-{uri-jsyntrax}[JSyntrax] is a reimplementation of Syntrax in Java in order to simplify installation, get rid of required libraries and make it easily portable to any operating system.
-
-== Supported Image Formats
-
-- PDF
-- PNG
-- SVG
-
-== Attributes
-
-[cols=">,<,<",options="header"]
-|===
-|Name          |Default value   |Description
-|syntrax       |syntrax         |The path to the `syntrax` executable. This attribute is used for the {uri-syntrax}[Syntrax] implementation.
-|java          |java            |The path to the `java` executable. This attribute is used for the {uri-jsyntrax}[JSyntrax] implementation. The `DIAGRAM_JSYNTRAX_HOME` environment variable should then also be defined and point to the JSyntrax installation directory. The installation directory can also be specified using the `diagram.jsyntrax.home` Java system property.
-|heading       |unspecified     |Diagram title
-|scale         |1               |A scale factor that is applied to the image.
-|style-file    |unspecified     |Path to a style config file to pass to Syntrax.
-|transparent   |false           |Makes the background of the image transparent instead of opaque white.
-|===

data/docs/modules/ROOT/pages/diagram_types/tikz.adoc

@@ -1,21 +0,0 @@
-= TikZ
-include::partial$uris.adoc[]
-
-{uri-tikz}[TikZ] is a graphics drawing environment for TeX.
-
-TikZ requires a TeX distribution that supports the {uri-tikz}[TikZ] package.
-
-== Supported Image Formats
-
-- PDF
-- SVG
-
-== Attributes
-
-[cols=">,<,<",options="header"]
-|===
-|Name          |Default value   |Description
-|pdflatex      |pdflatex        |The path to the `pdflatex` executable
-|pdf2svg       |pdf2svg         |The path to the `pdf2svg` executable
-|preamble      |unspecified     |Code definitions to pass to TikZ.
-|===

data/docs/modules/ROOT/pages/diagram_types/umlet.adoc

@@ -1,19 +0,0 @@
-= UMLet
-include::partial$uris.adoc[]
-
-{uri-umlet}[UMLet] is a free, open-source UML tool with a simple user interface: draw UML diagrams fast, create sequence and activity diagrams from plain text, share via exports to eps, pdf, jpg, svg, and clipboard, and develop new, custom UML elements.
-
-== Supported Image Formats
-
-- GIF
-- PDF
-- PNG
-- SVG
-
-== Attributes
-
-[cols=">,<,<",options="header"]
-|===
-|Name          |Default value   |Description
-|umlet         |umlet           |The path to the `umlet` executable
-|===

data/docs/modules/ROOT/pages/diagram_types/vega.adoc

@@ -1,28 +0,0 @@
-= Vega / Vega-Lite
-include::partial$uris.adoc[]
-
-{uri-vega}[Vega] and {uri-vegalite}[Vega-Lite] are declarative language for creating, saving, and sharing interactive visualization designs.
-
-Vega provides basic building blocks for a wide variety of visualization designs: data loading and transformation, scales, map projections, axes, legends, and graphical marks such as rectangles, lines, plotting symbols, etc.
-
-Vega-Lite provides a more concise and convenient form to author common visualizations. As Vega-Lite can compile its specifications to Vega specifications, users may use Vega-Lite as the primary visualization tool and, if needed, transition to use the lower-level Vega for advanced use cases.
-
-== Supported Image Formats
-
-- PNG
-- SVG
-
-== Attributes
-
-|vega         |{uri-vega}[vg2png] and/or {uri-vega}[vg2png]                          |`vg2png` and `vg2svg`
-|vegalite     |{uri-vegalite}[vl2vg] and {uri-vega}[vg2png] and/or {uri-vega}[vg2svg]|`vl2vg`, `vg2png` and `vg2svg`
-
-[cols=">,<,<",options="header"]
-|===
-|Name          |Default value   |Description
-|vg2png        |vg2png          |The path to the `vg2png` executable. This attribute is used for PNG output.
-|vg2svg        |vg2svg          |The path to the `vg2svg` executable This attribute is used for SVG output.
-|vl2vg         |vl2vg           |The path to the `vl2vg` executable. This attribute is used for Vega-Lite diagrams.
-|===
-
-None

data/docs/modules/ROOT/pages/diagram_types/wavedrom.adoc

@@ -1,17 +0,0 @@
-= WaveDrom
-include::partial$uris.adoc[]
-
-{uri-wavedrom}[WaveDrom] draws your Timing Diagram or Waveform from simple textual description.
-
-== Supported Image Formats
-
-- PNG
-- SVG
-
-== Attributes
-
-[cols=">,<,<",options="header"]
-|===
-|Name          |Default value   |Description
-|wavedrom      |wavedrom        |The path to the `wavedrom` executable
-|===

data/docs/modules/ROOT/pages/enabling.adoc

@@ -1,25 +0,0 @@
-= Enabling Extensions
-
-In your program, you can either load and register the entire set of diagram extensions
-
-[source,ruby]
-----
-require 'asciidoctor-diagram'
-----
-
-or load and register each extension individually.
-
-[source,ruby]
-----
-require 'asciidoctor-diagram/<extension_name>'
-----
-
-`<extension_name>` can be one of `a2s`, `blockdiag`, `bytefield`, `diagrams`, `ditaa`, `dpic`, `erd`, `gnuplot`, `graphviz`, `meme`, `mermaid`, `msc`, `pikchr`, `plantuml`, `shaape`, `smcat`, `svgbob`, `syntrax`, `umlet`, `vega` or `wavedrom`.
-
-Requiring one or more of these files will automatically register the extensions for all processed documents.
-
-If you need more fine-grained control over when the extensions are enabled, `asciidoctor-diagram/<extension_name>/extension` can be used instead.
-This loads the extensions but does not register it in the Asciidoctor extension registry.
-You can then manually register the extensions at the appropriate times using the `Asciidoctor::Extensions` API.
-
-This document explains the various features of asciidoctor-diagram blocks using ditaa diagrams as an example.

data/docs/modules/ROOT/pages/generate.adoc

@@ -1,15 +0,0 @@
-= Rendering Diagrams
-
-You can load Asciidoctor diagram in a terminal using the `-r` flag.
-
- $ asciidoctor -r asciidoctor-diagram sample.adoc
-
-You can also use Asciidoctor diagram with other converters, such as Asciidoctor EPUB.
-Asciidoctor-epub3 is also loaded with the `-r` flag.
-
- $ asciidoctor -r asciidoctor-diagram -r asciidoctor-epub3 -b epub3 sample.adoc
-
-Or, you can invoke Asciidoctor and the EPUB converter with the `asciidoctor-epub3` command.
-The command implicitly sets the `-r` and `-b` flags for EPUB3 output.
-
- $ asciidoctor-epub3 -r asciidoctor-diagram sample.adoc

data/docs/modules/ROOT/pages/index.adoc

@@ -1,12 +0,0 @@
-= Overview
-Pepijn Van_Eeckhoudt <https://github.com/pepijnve[@pepijnve]>; Sarah White <https://github.com/graphitefriction[@graphitefriction]>
-:description: README for the Asciidoctor Diagram extension for Asciidoctor.
-include::partial$uris.adoc[]
-
-Asciidoctor Diagram is a set of Asciidoctor extensions that enable rendering of plain text diagrams that are embedded in your AsciiDoc document as part of the Asciidoctor conversion process.
-
-Each extensions will invoke the necessary external diagram rendering tools to produce an image file which is inserted into your converted document.
-
-The extensions support the xref:diagram_types/a2s.adoc[], BlockDiag (xref:diagram_types/blockdiag.adoc[], xref:diagram_types/seqdiag.adoc[], xref:diagram_types/actdiag.adoc[], xref:diagram_types/nwdiag.adoc[]), xref:diagram_types/bytefield.adoc[], xref:diagram_types/dbml.adoc[], xref:diagram_types/ditaa.adoc[], xref:diagram_types/dpic.adoc[], xref:diagram_types/erd.adoc[Erd], xref:diagram_types/gnuplot.adoc[], xref:diagram_types/graphviz.adoc[], xref:diagram_types/lilypond.adoc[], xref:diagram_types/mermaid.adoc[], xref:diagram_types/msc.adoc[], xref:diagram_types/nomnoml.adoc[], xref:diagram_types/penrose.adoc[], xref:diagram_types/pikchr.adoc[], xref:diagram_types/plantuml.adoc[], xref:diagram_types/shaape.adoc[], xref:diagram_types/smcat.adoc[], xref:diagram_types/structurizr.adoc[], xref:diagram_types/svgbob.adoc[], xref:diagram_types/symbolator.adoc[], xref:diagram_types/syntrax.adoc[], xref:diagram_types/umlet.adoc[], xref:diagram_types/vega.adoc[], and xref:diagram_types/wavedrom.adoc[] syntax.
-
-Asciidoctor Diagram was inspired by the {uri-py-plantuml}[AsciiDoc PlantUML filter].

data/docs/modules/ROOT/pages/installation.adoc

@@ -1,32 +0,0 @@
-= Installation
-include::partial$uris.adoc[]
-
-Asciidoctor Diagram is a RubyGem, which can be installed using the `gem` or `bundle` commands.
-
-You can install the Asciidoctor Diagram gem by typing `gem install` in the CLI.
-
- $ gem install asciidoctor-diagram
-
-To install the gem using Bundler, first add the following entry to your project's [.path]_Gemfile_.
-
-.Gemfile
-[source,ruby]
-----
-gem 'asciidoctor-diagram'
-----
-
-Then execute `bundle` in the CLI.
-
- $ bundle
-
-== Diagram Renderer Installation Paths
-
-Asciidoctor Diagram depends on external tools to generate images.
-In most cases it will locate these tools automatically for you by looking for specific executables in each directory in the `PATH` environment variable.
-
-In case you've installed a tool in a way where the executable is not in the `PATH`, you can override its location manually using document attributes.
-If, for instance, you installed `diag_tool` in `/home/me/diag_tool/bin` and this path is not included in the `PATH` you can specify its location on the command line
-
- $ asciidoctor -a diag_tool=/home/me/actdiag/bin/diag_tool -r asciidoctor-diagram sample.adoc
-
-The exact document attributes to use are described in the documentation of each diagram type.

data/docs/modules/ROOT/pages/output.adoc

@@ -1,19 +0,0 @@
-= Output Directories
-
-== Image Output Directory
-
-When Asciidoctor Diagram writes images to disk it will go over the following options in order to determine where to write the files.
-
-. `\{imagesoutdir\}` if the `imagesoutdir` attribute has been specified
-. `\{outdir\}/\{imagesdir\}` if the `outdir` attribute has been specified
-. `\{to_dir\}/\{imagesdir\}` if the `to_dir` attribute has been specified
-. `\{base_dir\}/\{imagesdir\}`
-
-== Image Cache Directory
-
-The image generation also outputs metadata files that by default are located in `.asciidoctor/diagram`.
-To place them in different location, Asciidoctor Diagram checks for (in this order).
-
-. `\{cachedir\}` attribute is specified  in the block header (i.e. `[plantuml, png, cachedir=my-cache]`)
-. `\{diagram-cachedir\}` if the `diagram-cachedir` attribute has been specified
-. `\{outdir\}/\{imagesdir\}`

data/docs/modules/ROOT/partials/shared-attrs.adoc

@@ -1,12 +0,0 @@
-[cols=">,<,<",options="header"]
-|===
-|Name          |Default value   |Description
-|svg-type      |unspecified     |One of `static`, `inline` or `interactive`.
-This determines the style of SVG embedding that's used in certain backends.
-The xref:asciidoc:macros:image-svg.adoc[asciidoc spec] describes this in more detail.
-|server-url    |unspecified    |External service to render diagram.
-Usage removes the need to depend on external tools to be installed locally.
-|server-type   |unspecified    |One of `plantuml` or `kroki_io`
-|max-get-size  |1024           |The maximum size of the URI path for HTTP GET requests.
-If the maximum size is exceeded, POST requests are used instead
-|===

data/docs/modules/ROOT/partials/uris.adoc

@@ -1,48 +0,0 @@
-:uri-a2s: https://github.com/asciitosvg/asciitosvg
-:uri-actdiag: http://blockdiag.com/en/actdiag/index.html
-:uri-asciidoctor-api: http://asciidoctor.org/docs/user-manual/#api
-:uri-asciidoctor-extensions: http://asciidoctor.org/docs/user-manual/#extension-points
-:uri-blockdiag: http://blockdiag.com
-:uri-bpmn: https://github.com/gtudan/bpmn-js-cmd
-:uri-bytefield: https://github.com/Deep-Symmetry/bytefield-svg
-:uri-d2: https://d2lang.com
-:uri-dbml: https://github.com/softwaretechnik-berlin/dbml-renderer
-:uri-diagrams: https://diagrams.mingrammer.com
-:uri-ditaa: http://ditaa.sourceforge.net/
-:uri-dpic: https://gitlab.com/aplevich/dpic
-:uri-dot: https://graphviz.gitlab.io/_pages/doc/info/lang.html
-:uri-erd: https://github.com/BurntSushi/erd
-:uri-erd-go: https://github.com/kaishuu0123/erd-go
-:uri-gnuplot: http://gnuplot.info
-:uri-graphviz: https://graphviz.gitlab.io
-:uri-imagemagick: http://www.imagemagick.org
-:uri-java: http://java.sun.com
-:uri-jsyntrax: https://atp-mipt.github.io/jsyntrax/
-:uri-lilypond: https://lilypond.org
-:uri-mermaid: https://github.com/mermaid-js/mermaid-cli
-:uri-mscgen: http://www.mcternan.me.uk/mscgen/
-:uri-mscgen-js: https://github.com/mscgenjs/mscgenjs-cli
-:uri-nomnoml: http://nomnoml.com
-:uri-nwdiag: http://blockdiag.com/en/nwdiag/index.html
-:uri-packetdiag: http://blockdiag.com/en/nwdiag/index.html
-:uri-penrose: https://penrose.cs.cmu.edu
-:uri-phantomjs: http://phantomjs.org
-:uri-pikchr: https://pikchr.org
-:uri-plantuml: http://plantuml.sourceforge.net
-:uri-py-plantuml: https://code.google.com/p/asciidoc-plantuml/
-:uri-python: https://www.python.org
-:uri-rackdiag: http://blockdiag.com/en/nwdiag/index.html
-:uri-seqdiag: http://blockdiag.com/en/seqdiag/index.html
-:uri-shaape: https://github.com/christiangoltz/shaape
-:uri-smcat: https://github.com/sverweij/state-machine-cat
-:uri-structurizr: https://structurizr.com
-:uri-svgbob: https://github.com/ivanceras/svgbobrus
-:uri-symbolator: https://github.com/kevinpt/symbolator
-:uri-syntrax: https://kevinpt.github.io/syntrax/
-:uri-tikz: https://github.com/pgf-tikz/pgf
-:uri-umlet: http://www.umlet.com/
-:uri-vega: https://vega.github.io/vega/
-:uri-vegalite: https://vega.github.io/vega-lite/
-:uri-wavedrom: http://wavedrom.com
-:uri-wavedromeditor: https://github.com/wavedrom/wavedrom.github.io/releases
-:uri-wavedromcli: https://github.com/wavedrom/cli

data/examples/Gemfile

@@ -1,3 +0,0 @@
-source 'https://rubygems.org'
-
-gem "asciidoctor-diagram", :path => ".."

data/examples/README.adoc

@@ -1,18 +0,0 @@
-= Asciidoctor-diagram Examples
-
-This directory contains a number of example files that illustrate how to use the asciidoctor-diagram extension.
-
-In order to build the examples correctly the asciidoctor-diagram extension should be loaded.
-This can be done using bundler by running
-
-----
-bundle exec asciidoctor -r asciidoctor-diagram <asciidoc file>
-----
-
-If you do not want to use bundler you can alternatively run
-
-----
-asciidoctor -r asciidoctor-diagram -I ../lib <asciidoc file>
-----
-
-This variant requires you to explicitly specify the load path from which asciidoctor-diagram can be loaded.

data/examples/design.adoc

@@ -1,78 +0,0 @@
-= The design of Asciidoctor-diagram
-
-This document explains the design of Asciidoctor-diagram using PlantUML syntax.
-A detailed explanation of the PlantUML syntax is out scope for this document.
-This can be found on the http://www.plantuml.com[PlantUML web site].
-
-Asciidoctor-diagram is a simple Asciidoctor extension that enables embedding of diagrams inside asciidoc documents using various plain text diagram syntaxes.
-The current version of Asciidoctor-diagram support the Ditaa, Graphviz DOT and PlantUML syntax.
-
-Asciidoctor-diagram enables a number of new block types using the Asciidoctor `BlockProcessor` extension API.
-
-The main logic of the diagram generation is provided by the `DiagramBlock` module.
-This includes the shared options for the various blocks, checksum calculation of the diagram source code, cache validation and attribute generation for the generated output blocks.
-The DiagramBlock module also provides a means to register diagram output formats.
-
-When registering an output format, the registering code must specify a number of control parameters.
-The first parameter is the format name which controls when the generator is activated.
-The generator that is registered first determines the default format for the block.
-The second parameter is the output type of the generator.
-This is either `:image` or `:literal`.
-This parameter controls what type of block the `DiagramBlock` code will generate.
-Finally, a block should be provided that generates the diagram and returns it as a String.
-When called these blocks will receive the diagram source code and the parent Block as arguments.
-
-The actual `BlockProcessor` implementations include the `DiagramBlock` module and the appropriate generator module.
-The remainder of the implementation consists of registering format.
-
-The diagram below illustrates the relationship between the various classes and modules.
-
-.Asciidoctor-diagram class diagram
-[plantuml, "classes", align="center"]
-----
-namespace asciidoctor.extensions {
-  class BlockProcessor
-}
-
-namespace asciidoctor.diagram {
-  asciidoctor.extensions.BlockProcessor <|-- DitaaBlock
-  class DitaaGenerator << (M,#FF7700) >>
-
-  asciidoctor.extensions.BlockProcessor <|-- GraphvizBlock
-  asciidoctor.extensions.BlockProcessor <|-- PlantUmlBlock
-  class PlantUmlGenerator << (M,#FF7700) >>
-
-  class DiagramBlock << (M,#FF7700) >>
-
-  DitaaBlock --|> DitaaGenerator
-  DitaaBlock --|> DiagramBlock
-  GraphvizBlock --|> PlantUmlGenerator
-  GraphvizBlock --|> DiagramBlock
-  PlantUmlBlock --|> PlantUmlGenerator
-  PlantUmlBlock --|> DiagramBlock
-}
-----
-
-When Asciidoctor process a document it will invoke the block processors at the appropriate moment.
-The sequence of method calls for a Ditaa block is shown below.
-
-.Processing a Ditaa block
-[plantuml, "processing", align="center"]
-----
-Lexer->DiagramBlock : process
-activate DiagramBlock #FFBBBB
-
-DiagramBlock -> DiagramBlock: create_image_block
-activate DiagramBlock #DarkSalmon
-
-DiagramBlock -> DiagramBlock: code_checksum
-
-DiagramBlock -> DitaaGenerator: ditaa
-activate DitaaGenerator
-DiagramBlock <-- DitaaGenerator: image as String
-deactivate DitaaGenerator
-deactivate DiagramBlock
-
-Lexer <-- DiagramBlock: generated Block
-deactivate DiagramBlock
-----

data/examples/features.adoc

@@ -1,189 +0,0 @@
-= Asciidoctor-diagram features
-
-This document explains the various features of asciidoctor-diagram blocks using ditaa diagrams as an example.
-
-== Simple diagrams
-
-To mark a block as a diagram the appropriate style should be applied. This can be either `ditaa`, `graphviz` or `plantuml`.
-These styles can be applied to literal, listing or open blocks.
-
-A basic ditaa listing can be written as follows:
-
----------
-[ditaa]
-----
-                   +-------------+
-                   | asciidoctor |-------+
-                   |  diagram    |       |
-                   +-------------+       | png out
-                       ^                 |
-                       | ditaa in        |
-                       |                 v
- +--------+   +--------+----+    /---------------\
- |        | --+ asciidoctor +--> |               |
- |  Text  |   +-------------+    |Beatiful output|
- |Document|   |   !magic!   |    |               |
- |     {d}|   |             |    |               |
- +---+----+   +-------------+    \---------------/
-     :                                   ^
-     |          Lots of work             |
-     +-----------------------------------+
-----
----------
-
-results in the following image.
-
-[ditaa]
-----
-                   +-------------+
-                   | asciidoctor |-------+
-                   |  diagram    |       |
-                   +-------------+       | png out
-                       ^                 |
-                       | ditaa in        |
-                       |                 v
- +--------+   +--------+----+    /---------------\
- |        | --+ asciidoctor +--> |               |
- |  Text  |   +-------------+    |Beatiful output|
- |Document|   |   !magic!   |    |               |
- |     {d}|   |             |    |               |
- +---+----+   +-------------+    \---------------/
-     :                                   ^
-     |          Lots of work             |
-     +-----------------------------------+
-----
-
-== Controlling the file name
-
-The image above gets the file name `58372f7d2ceffae9e91fd0a7cbb080b6.png`.
-That long number is the checksum of the source code that was calculated by asciidoctor-diagram.
-If you want to give your generated files a more meaningful name, simply fill in the `target` attribute.
-
-This can be done by either specifying it as the first positional attribute or as a named attribute.
-Both examples below would result in a file called `ditaa-diagram.png`.
-
----------
-[ditaa, "ditaa-diagram"]
-----
-<snip>
-----
-
-[ditaa, target="ditaa-diagram"]
-----
-<snip>
-----
----------
-
-== Choosing an output format
-
-By default images are generated in `PNG` format.
-This can be overridden by defining the `format` (or 2nd positional) attribute.
-The set of supported formats is diagram type dependent.
-`ditaa` only supports the `png` format.
-`graphviz` supports `png` and `svg`.
-`plantuml` supports `png`, `svg` and `txt`.
-
-The `txt` format is perhaps a bit non-obvious.
-This generates an ascii art version of the UML diagrams.
-
-The following Graphviz DOT script
-
----------
-[graphviz, "dot_example", "svg"]
-----
-graph ethane {
-     C_0 -- H_0 [type=s];
-     C_0 -- H_1 [type=s];
-     C_0 -- H_2 [type=s];
-     C_0 -- C_1 [type=s];
-     C_1 -- H_3 [type=s];
-     C_1 -- H_4 [type=s];
-     C_1 -- H_5 [type=s];
-}
-----
----------
-
-generates an SVG representation of an ethane molecule footnote:[From http://en.wikipedia.org/wiki/DOT_(graph_description_language)#A_simple_example]
-
-[graphviz, "dot_example", "svg"]
-----
-graph ethane {
-     C_0 -- H_0 [type=s];
-     C_0 -- H_1 [type=s];
-     C_0 -- H_2 [type=s];
-     C_0 -- C_1 [type=s];
-     C_1 -- H_3 [type=s];
-     C_1 -- H_4 [type=s];
-     C_1 -- H_5 [type=s];
-}
-----
-
-With https://github.com/Alwinator/graphviz-py[graphviz_py] you can also use variables and Python code to do calculations:
-
-[graphviz_py, "graphviz_py_example", "svg"]
-----
-graph python_graph {
-{{
-import math
-
-value = 0.5
-sin = math.sin(value)
-cos = math.cos(value)
-}}
-
-A [label="{{= value }}"];
-B [label="{{= sin }}"];
-C [label="{{= cos }}"];
-
-A -- B [headlabel="sin"];
-A -- C [headlabel="cos"];
-
-}
-----
-
-Don't forget to install graphviz-py as described https://github.com/Alwinator/graphviz-py#installation[here].
-
-== Using standard asciidoc features
-
-Any remaining other attributes that are specified on a diagram block are copied over to the generated block.
-This means you can use the regular http://asciidoctor.org/docs/user-manual/#put-images-in-their-place[asciidoc positioning attributes] to place the diagrams where you want to.
-
-Block titles and block ids can also be applied in the same way to diagram blocks.
-
-As an example, the following block
-
---------
-[[plan]]
-.My plan to conquer the world
-[plantuml, align="center"]
---------
-
-results in a block with the correct caption and id applied to it.
-
-[[plan]]
-.My plan to conquer the world
-[plantuml, "activity_diagram", "svg", align="center"]
-----
-(*) --> "Create an Asciidoctor extension"
-"Create an Asciidoctor extension" --> " ? "
-" ? " --> "Profits!"
-"Profits!" --> (*)
-----
-
-== Loading diagrams from external files
-
-Asciidoctor-diagram also supports the various diagram block in block macro form.
-These are macros of the form `<name>::<target>[<attrlist>]`.
-
-In asciidoctor-diagram the macro names are identical to the block styles: `ditaa`, `graphviz` and `plantuml`
-The target is the path to the file containing the diagram source code.
-When the target is a relative path it is resolved with respect to the location of the document being processed.
-The attribute list behaves mostly the same as with the block styles.
-The only difference is that the `target` attribute is not supported.
-Instead the name of the generated image is derived from the target propery of the macro.
-
-The previous example in block macro form would look something like this with the text from the block located in a file called `activity_diagram.txt` instead of inline in the document.
-
-----
-plantuml::activity_diagram.txt[format="svg", align="center"]
-----