From: Skip Collins <skip.collins@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Grant Rettke <gcr@wisdomandwonder.com>
Subject: Re: Embedding an image in base64; exporting to ascii, html, and latex?
Date: Thu, 17 Apr 2014 14:38:46 -0400 [thread overview]
Message-ID: <CABUh-74KoLBuVKkjfvzCgpTjT23me=jp7x+Qo63rZ4=Lp56Q1Q@mail.gmail.com> (raw)
In-Reply-To: <8738hc6k1v.fsf@bzg.ath.cx>
> I see how base64 images can be used for HTML, but I don't know
> how to use them for LaTeX -- and I doubt it makes sense. But for
> HTML, yes, we can explore this feature... on my MAYBE list!
I would vote against inclusion of ascii-encoded binary files in org.
This violates the "it's just text" spirit of org.
On the other hand, it would be very nice for org-mode to support the
inclusion of org files in a zipped container. Developing a standard
folder structure to include images and other files in a single ".orgz"
that could be directly edited in emacs would be wonderful. This could
be very useful for doing reproducible research. It would allow easy
file exchange. Inclusion of specific export formats could also be
easily supported.
A quick test show that Emacs Archive mode already allows editing of
org files contained in zip files. Using external programs such as
latex almost works. An exported pdf file is generated correctly, but
it ends up not inside the zip file, but in the same folder that
contains the zip file. It has a name that starts with the zip
filename, but it has "/" and the intended name of the pdf file
appended.
It might not be that much work to fix export code and image import
macros to fully support a standard org archive format.
next prev parent reply other threads:[~2014-04-17 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 20:01 Embedding an image in base64; exporting to ascii, html, and latex? Grant Rettke
2014-04-08 1:43 ` Skip Collins
2014-04-17 15:40 ` Bastien
2014-04-17 18:38 ` Skip Collins [this message]
2014-04-17 18:49 ` Bastien
2014-04-18 13:27 ` Skip Collins
2014-04-18 13:37 ` Bastien
2014-04-19 20:37 ` John Kitchin
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='CABUh-74KoLBuVKkjfvzCgpTjT23me=jp7x+Qo63rZ4=Lp56Q1Q@mail.gmail.com' \
--to=skip.collins@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=gcr@wisdomandwonder.com \
/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).