From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Rettke Subject: Embedding an image in base64; exporting to ascii, html, and latex? Date: Mon, 7 Apr 2014 15:01:21 -0500 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e01229d10d9c83604f6795423 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52919) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXFjQ-0001vo-0u for emacs-orgmode@gnu.org; Mon, 07 Apr 2014 16:01:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WXFjP-0005wa-0m for emacs-orgmode@gnu.org; Mon, 07 Apr 2014 16:01:23 -0400 Received: from mail-ob0-x22d.google.com ([2607:f8b0:4003:c01::22d]:35107) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXFjO-0005wT-Rp for emacs-orgmode@gnu.org; Mon, 07 Apr 2014 16:01:22 -0400 Received: by mail-ob0-f173.google.com with SMTP id gq1so7141937obb.32 for ; Mon, 07 Apr 2014 13:01:21 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "emacs-orgmode@gnu.org" --089e01229d10d9c83604f6795423 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, Got curious about how one might embed an image in base64 encoding inside an org mode document and allow export to asciii, html, and latex. Goal is to keep the document all-in-one; so that users may work with the document and "worry about nothing else beyond that one document". Perhaps this isn't a new or good idea? Has it been done before? Searching yielded no results. Regards, Grant Rettke | AAAS, ACM, AMA, COG, FSF, IEEE, Sigma Xi grettke@acm.org | http://www.wisdomandwonder.com/ =E2=80=9CWisdom begins in wonder.=E2=80=9D --Socrates ((=CE=BB (x) (x x)) (=CE=BB (x) (x x))) =E2=80=9CLife has become immeasurably better since I have been forced to st= op taking it seriously.=E2=80=9D --Thompson --089e01229d10d9c83604f6795423 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

Got curious about how one might emb= ed an image in base64 encoding inside an org mode document and allow export=
to asciii, html, and latex.

Goal is to = keep the document all-in-one; so that users may work with the document
and "worry about nothing else beyond that one document".

Perhaps this isn't a new or good idea?
=
Has it been done before?

Searching = yielded no results.

Regards,

Grant Rettke | AAAS, ACM, AMA, COG, FSF, IEEE, Sigma Xi
=E2=80=9CWisdom begins in wonder.=E2=80=9D --Socrates
((=CE= =BB (x) (x x)) (=CE=BB (x) (x x)))
=E2=80=9CLife has become immea= surably better since I have been forced to stop taking it seriously.=E2=80= =9D --Thompson
--089e01229d10d9c83604f6795423-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Skip Collins Subject: Re: Embedding an image in base64; exporting to ascii, html, and latex? Date: Mon, 7 Apr 2014 21:43:54 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54448) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXL5E-0006p2-FQ for emacs-orgmode@gnu.org; Mon, 07 Apr 2014 21:44:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WXL5D-0004aX-Dv for emacs-orgmode@gnu.org; Mon, 07 Apr 2014 21:44:16 -0400 Received: from mail-oa0-x22f.google.com ([2607:f8b0:4003:c02::22f]:65088) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WXL5D-0004aR-8s for emacs-orgmode@gnu.org; Mon, 07 Apr 2014 21:44:15 -0400 Received: by mail-oa0-f47.google.com with SMTP id i11so292083oag.34 for ; Mon, 07 Apr 2014 18:44:14 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Grant Rettke Cc: "emacs-orgmode@gnu.org" On Mon, Apr 7, 2014 at 4:01 PM, Grant Rettke wrote: > Goal is to keep the document all-in-one Maybe have a look at this proposal for a zipped up org format, sort of like docx for MS Word: http://comments.gmane.org/gmane.emacs.orgmode/75454 It looks like there was some an attempt to implement the proposal. Using a zip file with a more-or-less standardized structure might help make org files, images, and configurations more portable. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Embedding an image in base64; exporting to ascii, html, and latex? Date: Thu, 17 Apr 2014 17:40:44 +0200 Message-ID: <8738hc6k1v.fsf@bzg.ath.cx> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40556) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WaoQo-0003Hv-GG for emacs-orgmode@gnu.org; Thu, 17 Apr 2014 11:41:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WaoQi-0002CN-G2 for emacs-orgmode@gnu.org; Thu, 17 Apr 2014 11:40:54 -0400 Received: from mail-we0-x229.google.com ([2a00:1450:400c:c03::229]:47518) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WaoQi-0002CC-5I for emacs-orgmode@gnu.org; Thu, 17 Apr 2014 11:40:48 -0400 Received: by mail-we0-f169.google.com with SMTP id w62so612931wes.0 for ; Thu, 17 Apr 2014 08:40:47 -0700 (PDT) In-Reply-To: (Grant Rettke's message of "Mon, 7 Apr 2014 15:01:21 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Grant Rettke Cc: "emacs-orgmode@gnu.org" Hi Grant, Grant Rettke writes: > Got curious about how one might embed an image in base64 encoding > inside an org mode document and allow export > to asciii, html, and latex. I somehow remember Ken Mankoff suggested this a while ago. 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! Thanks, -- Bastien From mboxrd@z Thu Jan 1 00:00:00 1970 From: Skip Collins Subject: Re: Embedding an image in base64; exporting to ascii, html, and latex? Date: Thu, 17 Apr 2014 14:38:46 -0400 Message-ID: References: <8738hc6k1v.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48119) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WarDI-0000iG-Np for emacs-orgmode@gnu.org; Thu, 17 Apr 2014 14:39:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WarDH-0001lc-Ts for emacs-orgmode@gnu.org; Thu, 17 Apr 2014 14:39:08 -0400 In-Reply-To: <8738hc6k1v.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: "emacs-orgmode@gnu.org" , Grant Rettke > 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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Embedding an image in base64; exporting to ascii, html, and latex? Date: Thu, 17 Apr 2014 20:49:12 +0200 Message-ID: <87zjjjx047.fsf@bzg.ath.cx> References: <8738hc6k1v.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49672) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WarNH-0006aS-4E for emacs-orgmode@gnu.org; Thu, 17 Apr 2014 14:49:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WarN5-0004uy-Qh for emacs-orgmode@gnu.org; Thu, 17 Apr 2014 14:49:27 -0400 Received: from mail-wg0-x229.google.com ([2a00:1450:400c:c00::229]:57969) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WarN5-0004uT-JF for emacs-orgmode@gnu.org; Thu, 17 Apr 2014 14:49:15 -0400 Received: by mail-wg0-f41.google.com with SMTP id n12so814332wgh.12 for ; Thu, 17 Apr 2014 11:49:14 -0700 (PDT) In-Reply-To: (Skip Collins's message of "Thu, 17 Apr 2014 14:38:46 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Skip Collins Cc: "emacs-orgmode@gnu.org" , Grant Rettke Skip Collins writes: > On the other hand, it would be very nice for org-mode to support the > inclusion of org files in a zipped container. How would that be different that zipping org files along with pictures and related needed content? -- Bastien From mboxrd@z Thu Jan 1 00:00:00 1970 From: Skip Collins Subject: Re: Embedding an image in base64; exporting to ascii, html, and latex? Date: Fri, 18 Apr 2014 09:27:44 -0400 Message-ID: References: <8738hc6k1v.fsf@bzg.ath.cx> <87zjjjx047.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53095) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wb8pq-0000e0-E9 for emacs-orgmode@gnu.org; Fri, 18 Apr 2014 09:28:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wb8pp-0006jm-73 for emacs-orgmode@gnu.org; Fri, 18 Apr 2014 09:28:06 -0400 In-Reply-To: <87zjjjx047.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: "emacs-orgmode@gnu.org" , Grant Rettke On Thu, Apr 17, 2014 at 2:49 PM, Bastien 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: . =E2=94=9C=E2=94=80=E2=94=80 [Content_Types].xml =E2=94=9C=E2=94=80=E2=94=80 _rels =E2=94=9C=E2=94=80=E2=94=80 docProps =E2=94=82 =E2=94=9C=E2=94=80=E2=94=80 app.xml =E2=94=82 =E2=94=9C=E2=94=80=E2=94=80 core.xml =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 thumbnail.jpeg =E2=94=94=E2=94=80=E2=94=80 word =E2=94=9C=E2=94=80=E2=94=80 _rels =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 document.xml.rels =E2=94=9C=E2=94=80=E2=94=80 document.xml =E2=94=9C=E2=94=80=E2=94=80 fontTable.xml =E2=94=9C=E2=94=80=E2=94=80 media =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 image1.png =E2=94=9C=E2=94=80=E2=94=80 settings.xml =E2=94=9C=E2=94=80=E2=94=80 styles.xml =E2=94=9C=E2=94=80=E2=94=80 stylesWithEffects.xml =E2=94=9C=E2=94=80=E2=94=80 theme =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 theme1.xml =E2=94=94=E2=94=80=E2=94=80 webSettings.xml An analogous structure inside a filename.orgz container might be useful. Perhaps something like: . =E2=94=9C=E2=94=80=E2=94=80 orgmain.org =E2=94=9C=E2=94=80=E2=94=80 config.org =E2=94=9C=E2=94=80=E2=94=80 media =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 image1.png =E2=94=9C=E2=94=80=E2=94=80 elisp =E2=94=82 =E2=94=9C=E2=94=80=E2=94=80 init.el =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 myorgmacros.el =E2=94=9C=E2=94=80=E2=94=80 babel =E2=94=94=E2=94=80=E2=94=80 export =E2=94=9C=E2=94=80=E2=94=80 styles =E2=94=94=E2=94=80=E2=94=80 output =E2=94=9C=E2=94=80=E2=94=80 orgmain.pdf =E2=94=94=E2=94=80=E2=94=80 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. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Embedding an image in base64; exporting to ascii, html, and latex? Date: Fri, 18 Apr 2014 15:37:39 +0200 Message-ID: <87k3amkbbw.fsf@bzg.ath.cx> References: <8738hc6k1v.fsf@bzg.ath.cx> <87zjjjx047.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55692) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wb8zK-000823-Dr for emacs-orgmode@gnu.org; Fri, 18 Apr 2014 09:38:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wb8zB-0001n7-Ch for emacs-orgmode@gnu.org; Fri, 18 Apr 2014 09:37:54 -0400 Received: from mail-wi0-x230.google.com ([2a00:1450:400c:c05::230]:53823) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wb8zB-0001my-6c for emacs-orgmode@gnu.org; Fri, 18 Apr 2014 09:37:45 -0400 Received: by mail-wi0-f176.google.com with SMTP id r20so717355wiv.9 for ; Fri, 18 Apr 2014 06:37:44 -0700 (PDT) In-Reply-To: (Skip Collins's message of "Fri, 18 Apr 2014 09:27:44 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Skip Collins Cc: "emacs-orgmode@gnu.org" , Grant Rettke Hi Skip, I now see how this could be useful for sharing documents with Org files and Emacs configuration bits, but I doubt this would prove really useful: in LibreOffice, the bundle makes sense because it contains all what people need for both reading and writing docs; while in Emacs land, Org are more for writing and their PDF/HTML output for reading... not sure if my point is clear, I hope so -- that said, I like your idea and would be glad to see how it could work practically. -- Bastien From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: Embedding an image in base64; exporting to ascii, html, and latex? Date: Sat, 19 Apr 2014 16:37:19 -0400 Message-ID: References: <8738hc6k1v.fsf@bzg.ath.cx> <87zjjjx047.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=e89a8f13ed208f64dc04f76b3b05 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44330) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wbc0p-00063Z-W0 for emacs-orgmode@gnu.org; Sat, 19 Apr 2014 16:37:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wbc0o-0003z1-Fc for emacs-orgmode@gnu.org; Sat, 19 Apr 2014 16:37:23 -0400 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Skip Collins Cc: Bastien , "emacs-orgmode@gnu.org" , Grant Rettke --e89a8f13ed208f64dc04f76b3b05 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 wrote= : > On Thu, Apr 17, 2014 at 2:49 PM, Bastien 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: > . > =E2=94=9C=E2=94=80=E2=94=80 [Content_Types].xml > =E2=94=9C=E2=94=80=E2=94=80 _rels > =E2=94=9C=E2=94=80=E2=94=80 docProps > =E2=94=82 =E2=94=9C=E2=94=80=E2=94=80 app.xml > =E2=94=82 =E2=94=9C=E2=94=80=E2=94=80 core.xml > =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 thumbnail.jpeg > =E2=94=94=E2=94=80=E2=94=80 word > =E2=94=9C=E2=94=80=E2=94=80 _rels > =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 document.xml.rels > =E2=94=9C=E2=94=80=E2=94=80 document.xml > =E2=94=9C=E2=94=80=E2=94=80 fontTable.xml > =E2=94=9C=E2=94=80=E2=94=80 media > =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 image1.png > =E2=94=9C=E2=94=80=E2=94=80 settings.xml > =E2=94=9C=E2=94=80=E2=94=80 styles.xml > =E2=94=9C=E2=94=80=E2=94=80 stylesWithEffects.xml > =E2=94=9C=E2=94=80=E2=94=80 theme > =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 theme1.xml > =E2=94=94=E2=94=80=E2=94=80 webSettings.xml > > An analogous structure inside a filename.orgz container might be > useful. Perhaps something like: > . > =E2=94=9C=E2=94=80=E2=94=80 orgmain.org > =E2=94=9C=E2=94=80=E2=94=80 config.org > =E2=94=9C=E2=94=80=E2=94=80 media > =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 image1.png > =E2=94=9C=E2=94=80=E2=94=80 elisp > =E2=94=82 =E2=94=9C=E2=94=80=E2=94=80 init.el > =E2=94=82 =E2=94=94=E2=94=80=E2=94=80 myorgmacros.el > =E2=94=9C=E2=94=80=E2=94=80 babel > =E2=94=94=E2=94=80=E2=94=80 export > =E2=94=9C=E2=94=80=E2=94=80 styles > =E2=94=94=E2=94=80=E2=94=80 output > =E2=94=9C=E2=94=80=E2=94=80 orgmain.pdf > =E2=94=94=E2=94=80=E2=94=80 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. > > --e89a8f13ed208f64dc04f76b3b05 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It doesn't do anything fancy like you describe, but it does g= et images and files into the zip file.
=
John

-----------------------------------
J= ohn Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Enginee= ring
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803<= br>http://k= itchingroup.cheme.cmu.edu



On Fri, Apr 18, 2014 at 9:27 AM, Skip Co= llins <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:
.
=E2=94=9C=E2=94=80=E2=94=80 [Content_Types].xml
=E2=94=9C=E2=94=80=E2=94=80 _rels
=E2=94=9C=E2=94=80=E2=94=80 docProps
=E2=94=82 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 app.xml
=E2=94=82 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 core.xml
=E2=94=82 =C2=A0 =E2=94=94=E2=94=80=E2=94=80 thumbnail.jpeg
=E2=94=94=E2=94=80=E2=94=80 word
=C2=A0 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 _rels
=C2=A0 =C2=A0 =E2=94=82 =C2=A0 =E2=94=94=E2=94=80=E2=94=80 document.xml.rel= s
=C2=A0 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 document.xml
=C2=A0 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 fontTable.xml
=C2=A0 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 media
=C2=A0 =C2=A0 =E2=94=82 =C2=A0 =E2=94=94=E2=94=80=E2=94=80 image1.png
=C2=A0 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 settings.xml
=C2=A0 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 styles.xml
=C2=A0 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 stylesWithEffects.xml
=C2=A0 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 theme
=C2=A0 =C2=A0 =E2=94=82 =C2=A0 =E2=94=94=E2=94=80=E2=94=80 theme1.xml
=C2=A0 =C2=A0 =E2=94=94=E2=94=80=E2=94=80 webSettings.xml

An analogous structure inside a filename.orgz container might be
useful. Perhaps something like:
.
=E2=94=9C=E2=94=80=E2=94=80 orgmain.org
=E2=94=9C=E2=94=80=E2=94=80 config.org
=E2=94=9C=E2=94=80=E2=94=80 media
=E2=94=82 =C2=A0 =E2=94=94=E2=94=80=E2=94=80 image1.png
=E2=94=9C=E2=94=80=E2=94=80 elisp
=E2=94=82 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 init.el
=E2=94=82 =C2=A0 =E2=94=94=E2=94=80=E2=94=80 myorgmacros.el
=E2=94=9C=E2=94=80=E2=94=80 babel
=E2=94=94=E2=94=80=E2=94=80 export
=C2=A0 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 styles
=C2=A0 =C2=A0 =E2=94=94=E2=94=80=E2=94=80 output
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=94=9C=E2=94=80=E2=94=80 orgmain.pdf
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =E2=94=94=E2=94=80=E2=94=80 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.


--e89a8f13ed208f64dc04f76b3b05--