From mboxrd@z Thu Jan 1 00:00:00 1970 From: tsd@tsdye.com (Thomas S. Dye) Subject: Re: [ANN] ASCII back-end for new export engine Date: Sun, 22 Jan 2012 19:58:24 -1000 Message-ID: References: <87pqec4xua.fsf@gmail.com> <87obtvk6j0.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([140.186.70.92]:42428) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RpCv6-0005jn-F4 for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 00:58:21 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RpCv4-00042t-MJ for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 00:58:20 -0500 Received: from oproxy7-pub.bluehost.com ([67.222.55.9]:53893) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RpCv4-00042e-Bz for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 00:58:18 -0500 In-Reply-To: <87obtvk6j0.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 22 Jan 2012 18:10:11 +0100") 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: Nicolas Goaziou Cc: Org Mode List Aloha Nicolas, Nicolas Goaziou writes: > Hello, > > tsd@tsdye.com (Thomas S. Dye) writes: > >> A quick question and a couple of comments on the LaTeX exporter. >> >> With the old exporter I set (setq org-export-latex-hyperref-format >> "\\ref{%s}") so a link to a headline would cross reference properly in >> LaTeX. How do I achieve this with the new exporter? I want my text to >> read, e.g., "In section 1 ..." So far with the new exporter, I've only >> been able to get "In section First headline ..." > > Indeed, it seems that I forgot to create that variable in the new > exporter. I don't mind adding it, but I'm not sure about where it should > apply. > > At the moment, "\\hyperref[%s]{%s}" format string is applied to id, > custom-id, target, radio, fuzzy/target and fuzzy/headline links. > Changing all those links with just a single variable seems wrong to me. > > Maybe it should replace the default value only for id, custom-id and > fuzzy/headline. And since it would only apply to headlines, it could be > renamed `org-e-latex-link-to-headline-format' or something alike. > > What do you think about all of this? I think that your understanding of the new exporter architecture is intimate and secure. I'm happy to follow your lead here. > >> My initial impression is the new exporter is extremely fast. > > Unfortunately, it's only an impression. It will be slower than the > current exporter in most cases. > I'm sure the difference (which I haven't detected) will be outweighed by the benefits of the new exporter. > Oh, by the way, it reminds me that I implemented something in the LaTeX > back-end that you had asked for a while ago. If you didn't notice it, > you can try a LaTeX export on the following test buffer: > > #+latex_header: \usepackage{paralist} > > * Head 1 > > Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do > eiusmod tempor incididunt ut labore et dolore magna aliqua. > #+attr_latex: inparaenum i. > - item 1 > - item 2 > Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do > eiusmod tempor incididunt ut labore et dolore magna aliqua. > > There is support for the following keywords: inparaenum, asparaenum, > inparaitem, asparaitem, inparadesc, asparadesc, all accepting an > optional bullet argument. I hadn't noticed this yet. It looks like a terrific example of the power of your parser. Many thanks for this functionality. It will take me a while to understand the practical implications of the level to which you have abstracted Org mode, but I look forward to the challenge. I also look forward to the pleasure of using the new LaTeX exporter. Thanks again for your good work. All the best, Tom -- Thomas S. Dye http://www.tsdye.com