From mboxrd@z Thu Jan 1 00:00:00 1970 From: Suvayu Ali Subject: Re: text-only plots Date: Tue, 10 Dec 2013 00:55:39 +0100 Message-ID: <20131209235539.GH20815@kuru.dyndns-at-home.com> References: <20131209121923.GD20815@kuru.dyndns-at-home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46843) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqAg5-0008LZ-CB for emacs-orgmode@gnu.org; Mon, 09 Dec 2013 18:56:01 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VqAfw-0007zY-T6 for emacs-orgmode@gnu.org; Mon, 09 Dec 2013 18:55:53 -0500 Received: from mail-wg0-x22d.google.com ([2a00:1450:400c:c00::22d]:49957) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqAfw-0007zK-JR for emacs-orgmode@gnu.org; Mon, 09 Dec 2013 18:55:44 -0500 Received: by mail-wg0-f45.google.com with SMTP id y10so4148150wgg.0 for ; Mon, 09 Dec 2013 15:55:43 -0800 (PST) Received: from kuru.dyndns-at-home.com (sd44012d5.adsl.online.nl. [212.64.18.213]) by mx.google.com with ESMTPSA id f11sm90916wic.4.2013.12.09.15.55.41 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Dec 2013 15:55:42 -0800 (PST) Content-Disposition: inline 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: emacs-orgmode@gnu.org Hi Thiery, On Mon, Dec 09, 2013 at 10:48:22PM +0000, Thierry Banel wrote: > Ivan Andrus gmail.com> writes: > > On Dec 9, 2013, at 5:19 AM, Suvayu Ali gmail.com> > wrote: > > > Technically speaking, it is not exported as a table since you put it as > > > part of example block. However a quick test tells me, html export will > > > work fine (screenshot attached). However LaTeX export is an entirely > > > different story. Unicode support in normal pdflatex is quite > > > non-trivial. If you use XeLaTeX, I think you could get it to work with > > > some appropriate choice of fonts. I tried libertine and dejavu without > > > any luck. > > > > Would it be possible to export it to \rule when using LaTeX? It > > wouldn't be text then and you couldn't copy it, but it should work > > with any TeX engine regardless of fonts etc. Just a thought. > > Right, Suvayu, Unicodes are not universally supported. > So, what about coming back to basics ? > Just Ascii like that: [...chomp...chomp...chomp...] > We remove Unicodes until someone comes with an idea. > > Ivan, the LaTex \rule might be a (pretty) solution for the LaTex exporter. > But then we should also take care of all past and future exporters... Firstly, I think the unicode bit is a terrific improvement; specially the two options: grid and continuous. I think there are two distinct problems here: the plot as shown in org, and export. We should not confuse the two. I will suggest for the moment having the plotting bits is enough. HTML export works, plain text export sort of works[1]. As you see, getting it right for all (most) exporters is non-trivial, so I would say no need for worrying about supporting past exporters. Handling this needs some conditional behaviour: plain text -> backend, or unicode -> backend. You could use a standardised column title to selectively choose/ignore columns. So ASCII export would ignore unicode columns. LaTeX export would replace the chars with appropriate symbols (e.g. \rule, as suggested by Ivan). Texinfo and markdown supports unicode, so that should be fine (like HTML). When we have something that is acceptable, you can publish the exporter code and the plotting code as part of the same module, say org-ascii-plot.el (or something along those lines). Which could then go in contrib. WDYT? Footnotes: [1] Sort-of, because it "lies" by including unicode chars even if you export to ASCII only. -- Suvayu Open source is the future. It sets us free.