From: Peter Davis <pfd@pfdstudio.com>
To: emacs-orgmode@gnu.org
Subject: Remaining document problems
Date: Wed, 12 Oct 2016 10:55:26 -0400 [thread overview]
Message-ID: <1476284126.2405843.753686713.71418D96@webmail.messagingengine.com> (raw)
After days and days of wrestling with this, I still seem to be unable to
solve some basic problems:
A. Source code listings
1) Source code blocks: Using
#+BEGIN_SRC js
works for HTML output, but not for LaTeX/PDF. It seems js is not
understood by the listings package, and I have to use java.
2) Even with java, the output is pretty ugly. Any way to get some color
in there?
B. Graphics
I've tried TikZ, GraphViz dot and ditaa. I believe TikZ has the most
potential, once I learn all the options and attributes. However, I'm
stuck on a couple of things:
1) How to I get TikZ graphics to fit on a page? The TikZ pictures are
always on a separate page in my org PDF output.
2) I'd really like to get all my graphics in SVG format, so the text
would be searchable, clickable, etc. However, I haven't found a way to
get TikZ output into SVG, or to get SVG into LaTeX. (Yes, I'm aware of
the svg package, which requires Inkscape, but even after installing
that, I can't get svg images to work in LaTeX.)
I've Googled all of these, and tried to understand the answers, though
many take a complete understanding of yet another package/tool/etc. It's
getting very discouraging. I'd really like to use org-mode, but I'm
wondering if AsciiDoc or even MarkDown might be easier.
Thanks,
-pd
--
Peter Davis
www.techcurmudgeon.com
next reply other threads:[~2016-10-12 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 14:55 Peter Davis [this message]
2016-10-12 15:39 ` Remaining document problems Nick Dokos
2016-10-12 16:35 ` Peter Davis
[not found] ` <463a5687c70841b8a6603102739fbf02@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-13 8:08 ` Eric S Fraga
2016-10-13 12:46 ` Peter Davis
[not found] ` <1da24f56addb4163963006cdae9703cb@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-13 13:01 ` Eric S Fraga
2016-10-13 13:03 ` Eric S Fraga
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=1476284126.2405843.753686713.71418D96@webmail.messagingengine.com \
--to=pfd@pfdstudio.com \
--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).