emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Skip Collins <skip.collins@gmail.com>
Cc: Bastien <bzg@gnu.org>,
	"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: Sat, 19 Apr 2014 16:37:19 -0400	[thread overview]
Message-ID: <CAJ51ETpnTHLCTTaaSPi6EuMVw2VWRuiQpnvrFuN-Qb2us1N5rg@mail.gmail.com> (raw)
In-Reply-To: <CABUh-74XSO1q1EUYJVAPB00FOag1eJkaUMMLjgx5qJa_KwEbjQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2832 bytes --]

I wrote some code that does some of this here:
http://kitchingroup.cheme.cmu.edu/blog/2014/03/05/Creating-a-transportable-zip-archive-of-an-org-file/

It doesn't do anything fancy like you describe, but it does get images and
files into the zip file.

John

-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu



On Fri, Apr 18, 2014 at 9:27 AM, Skip Collins <skip.collins@gmail.com>wrote:

> On Thu, Apr 17, 2014 at 2:49 PM, Bastien <bzg@gnu.org> wrote:
> > How would that be different that zipping org files along with pictures
> > and related needed content?
>
> Not different at all. Integrating the zipping into org-mode itself
> could standardize the process and make it more
> repeatable, portable, and convenient. Microsoft Word .docx files have
> something like this structure inside:
> .
> ├── [Content_Types].xml
> ├── _rels
> ├── docProps
> │   ├── app.xml
> │   ├── core.xml
> │   └── thumbnail.jpeg
> └── word
>     ├── _rels
>     │   └── document.xml.rels
>     ├── document.xml
>     ├── fontTable.xml
>     ├── media
>     │   └── image1.png
>     ├── settings.xml
>     ├── styles.xml
>     ├── stylesWithEffects.xml
>     ├── theme
>     │   └── theme1.xml
>     └── webSettings.xml
>
> An analogous structure inside a filename.orgz container might be
> useful. Perhaps something like:
> .
> ├── orgmain.org
> ├── config.org
> ├── media
> │   └── image1.png
> ├── elisp
> │   ├── init.el
> │   └── myorgmacros.el
> ├── babel
> └── export
>     ├── styles
>     └── output
>         ├── orgmain.pdf
>         └── orgmain.html
>
> A little elisp wizardry could ensure that invoking
> emacs filename.orgz
> would actually open and edit orgmain.org inside filename.orgz.
>
> Much of the tree structure could be optional, only included when
> certain features are used. Obviously, it would be necessary to put
> exported files outside of the .orgz file. But optionally including a
> copy inside could be useful. More important would be the inclusion of
> all non-standard input files needed to generate the output, things
> like images, elisp files, latex and html style files, etc. Maybe even
> a copy of the Emacs initialization file used when saving the container
> file. Finally, a standardized format for config.org would include
> things like Emacs version, Org version, creation date, modification
> date, a list of manually included files, etc.
>
>

[-- Attachment #2: Type: text/html, Size: 3797 bytes --]

      parent reply	other threads:[~2014-04-19 20:37 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
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 [this message]

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=CAJ51ETpnTHLCTTaaSPi6EuMVw2VWRuiQpnvrFuN-Qb2us1N5rg@mail.gmail.com \
    --to=jkitchin@andrew.cmu.edu \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=gcr@wisdomandwonder.com \
    --cc=skip.collins@gmail.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).