emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: Creating a (RabbitMQ) diagram
Date: Sat, 19 Oct 2019 10:50:49 +0200	[thread overview]
Message-ID: <877e51p192.fsf@luisa.c0t0d0s0.de> (raw)
In-Reply-To: <xuu6mudy1j6m.fsf@ucl.ac.uk> (Eric Fraga's message of "Fri, 18 Oct 2019 09:45:06 +0000")

Hello,

"Fraga, Eric" <e.fraga@ucl.ac.uk> writes:

> On Thursday, 17 Oct 2019 at 15:21, Cecil Westerhof wrote:
>> I tried it out (after a bit of configuring) with the following:
>>
>> #+BEGIN_SRC plantuml :file groupingComponents.eps :noexport
>
> [...]
>
>> It looks a bit different, but I will not worry about it at the moment.
>
> I use the following tools within org for eventual export to PDF via
> latex: tikz, ditaa, graphviz (dot, neato, ...), & plantuml.  I've even
> bee known to use LaTeX's own picture environmnt.  They each have
> different advantages and disadvantages but all work well with org in my
> opinion.
so think and do I. At the moment I try to consolidate the tools I use
and try to get away with tikz only. I tried to reproduce same diagrams I
created with plantuml. Well, it works. But there are a lot of details in
plantuml's output that you have to do manually with tikz. BTW, I just
discovered that plantuml's pdf output is way different from its LaTeX
output.

Regards
hmw

  reply	other threads:[~2019-10-19  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 11:01 Creating a (RabbitMQ) diagram Cecil Westerhof
2019-10-17 11:12 ` PICCA Frederic-Emmanuel
2019-10-17 11:40   ` Ken Mankoff
2019-10-17 13:21     ` Cecil Westerhof
2019-10-18  9:45       ` Fraga, Eric
2019-10-19  8:50         ` Michael Welle [this message]
2019-10-17 14:01     ` Cecil Westerhof
2019-10-17 20:03   ` Marcin Borkowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877e51p192.fsf@luisa.c0t0d0s0.de \
    --to=mwe012008@gmx.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).