From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Newsgroups: gmane.emacs.help Subject: Re: want a file format easily edited and read by emacs that allows (multiple) pictures to be included Date: Tue, 5 Dec 2017 12:39:35 +0100 Message-ID: <20171205113935.GI22742@tuxteam.de> References: <87indo7s7o.fsf@mbork.pl> <87d13u7qvo.fsf@mbork.pl> <86a7yydw9n.fsf@zoho.com> <20171204215223.GB1723@tuxteam.de> <86609mduhp.fsf@zoho.com> <20171204221250.GF1723@tuxteam.de> <86o9nddd7i.fsf@zoho.com> <87a7yxijlp.fsf@delle7240.chemeng.ucl.ac.uk> <86indlbeqm.fsf@zoho.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1512474016 31936 195.159.176.226 (5 Dec 2017 11:40:16 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 5 Dec 2017 11:40:16 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Tue Dec 05 12:40:09 2017 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eMBa1-0007qZ-Ew for geh-help-gnu-emacs@m.gmane.org; Tue, 05 Dec 2017 12:40:05 +0100 Original-Received: from localhost ([::1]:47983 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eMBa7-000206-F2 for geh-help-gnu-emacs@m.gmane.org; Tue, 05 Dec 2017 06:40:11 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43862) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eMBZg-0001zw-7L for help-gnu-emacs@gnu.org; Tue, 05 Dec 2017 06:39:45 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eMBZc-00029v-63 for help-gnu-emacs@gnu.org; Tue, 05 Dec 2017 06:39:44 -0500 Original-Received: from mail.tuxteam.de ([5.199.139.25]:47869) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eMBZb-00029V-Ok for help-gnu-emacs@gnu.org; Tue, 05 Dec 2017 06:39:40 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=20171004; h=From:In-Reply-To:Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID:Subject:To:Date; bh=t/P/3UnpImjd9M8uQX93C8xw38kNWALZb5ELcNvnEig=; b=iQRN/f9pyo33JQ6SgN5AtFWxxvNor+NouF4RybsNOmy2upQvpd1hV1PC2Dw3VoOxJXMpcubYC6W7zd/K4VdiTVzn07R47GiQ6HtCRtaYMK/KXYZXkTPVcMEbkWa6Df16oHsphPxV2cqVyEJg52NxvLSicy4aawWl7Oe+ID6orpoW/ZVGsyN8fM1K4xW0FlaxoEag8b2UvpawBPq/A88yolakA6czRJ5xPFU4OT0093jP8OXx66YlnaWLL4xbo34UHb9+l1Yt+qSnPzh8vaqMuEkp6ZibJqldmL87hq53CHrN6fuVZCXF0zDYZad4aUWdAbxz+Sl0FGV5p2gepn9O+A==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.80) (envelope-from ) id 1eMBZX-0007Y7-U8 for help-gnu-emacs@gnu.org; Tue, 05 Dec 2017 12:39:35 +0100 In-Reply-To: <86indlbeqm.fsf@zoho.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 5.199.139.25 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:115214 Archived-At: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Dec 05, 2017 at 12:23:13PM +0100, Emanuel Berg wrote: > Eric S Fraga wrote: > > > I sometimes have the need to create > > a self-contained document for sharing with > > others. Using the little snippet of elisp > > that Marcin posted allows me to do so quite > > easily. Previously, I would need to create > > a tar/zip file with all the images. Very nice > > solution for my requirements. > > The "all in an Emacs buffer" is appealing but > the Achille's Heel is that an Emacs buffer, > compared to a PDF document or HTML website, is > a cup from which only a select few dare > drink... *This* is actually the one interesting point. That said, even Github (the horrors!) understands Org syntax. The syntax itself has a few downsides, IMHO, but it is way cleaner than Markdown with its ugly HTML escape hatch. > As for me, it feels like all the wonders > I create already have a minimal audience. > To a huge part, this is a human, not technology > problem. But I don't want to put up even more > palisades. Besides, I have no problem with > LaTeX or HTML. So I always want to use the > biggest thing which still is to my liking. > So far, that has meant small enough things as > it is... The point is that LaTeX (and HTML) are, as actually used, in a different point in space, much more concerned with appearance and less with structure. At least for LaTeX, you might argue that you can choose that yourself, because the *mechanism* of abstraction is there, but success has been modest. As to HTML... a format mainly in the hands of the W3C (club of the richest Internet consortia), oh, well. I prefer to treat that one as write-only. There's a place for more content-oriented, more easily editable, more plain-texty language. And these are Markdown, Python's reStructuredText, Perl's POD, and many other lightweight markup languages [1] among which... org comes with a built-in powerful editor we all love :-) Cheers [1] https://en.wikipedia.org/wiki/Lightweight_markup_language - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlomhXcACgkQBcgs9XrR2kYx7gCfU63XMehioQ32G/rv6QAe32xB 1aYAn07xBJycn2wPzV1p1uaII3VioS4z =8Twh -----END PGP SIGNATURE-----