From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [ANN] ASCII back-end for new export engine
Date: Sun, 22 Jan 2012 18:10:11 +0100 [thread overview]
Message-ID: <87obtvk6j0.fsf@gmail.com> (raw)
In-Reply-To: <m11uqr4rw5.fsf@tsdye.com> (Thomas S. Dye's message of "Sun, 22 Jan 2012 06:35:22 -1000")
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?
> 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.
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:
--8<---------------cut here---------------start------------->8---
#+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.
--8<---------------cut here---------------end--------------->8---
There is support for the following keywords: inparaenum, asparaenum,
inparaitem, asparaitem, inparadesc, asparadesc, all accepting an
optional bullet argument.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-01-22 17:12 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 20:14 [ANN] ASCII back-end for new export engine Nicolas Goaziou
2012-01-21 20:33 ` Samuel Wales
2012-01-21 20:36 ` Samuel Wales
2012-01-21 23:04 ` Nicolas Goaziou
2012-01-22 1:28 ` Samuel Wales
2012-01-22 9:43 ` Nicolas Goaziou
2012-01-22 16:36 ` Samuel Wales
2012-01-28 10:28 ` Samuel Wales
2012-01-28 13:55 ` Nicolas Goaziou
2012-01-28 20:50 ` Samuel Wales
2012-01-28 21:32 ` Nicolas Goaziou
2012-01-28 22:15 ` Samuel Wales
2012-01-28 23:58 ` Nicolas Goaziou
2012-01-22 14:43 ` Martyn Jago
2012-01-22 15:45 ` Nicolas Goaziou
2012-01-22 16:43 ` Martyn Jago
2012-01-23 20:05 ` Eric Schulte
2012-01-23 20:49 ` Nicolas Goaziou
2012-01-22 16:35 ` Thomas S. Dye
2012-01-22 17:10 ` Nicolas Goaziou [this message]
2012-01-23 5:58 ` Thomas S. Dye
2012-01-25 17:41 ` Nicolas Goaziou
2012-01-26 6:49 ` Tweaking the export (was: Re: [ANN] ASCII back-end for new export engine) Christian Wittern
2012-01-27 13:06 ` Tweaking the export Nicolas Goaziou
2012-01-27 13:47 ` Jambunathan K
2012-01-27 14:03 ` Sebastien Vauban
2012-01-28 2:33 ` Christian Wittern
2012-01-28 2:21 ` Christian Wittern
2012-01-28 4:03 ` Eric Abrahamsen
2012-01-29 9:07 ` Nicolas Goaziou
2012-02-04 6:21 ` Christian Wittern
2012-02-17 20:06 ` Nicolas Goaziou
2012-01-26 8:44 ` [ANN] ASCII back-end for new export engine Eric S Fraga
2012-01-26 13:59 ` Thomas S. Dye
2012-01-26 15:28 ` Nicolas Goaziou
2012-01-26 17:32 ` Thomas S. Dye
2012-01-26 18:31 ` Nicolas Goaziou
2012-01-26 19:00 ` Achim Gratz
2012-01-27 12:58 ` Nicolas Goaziou
2012-01-27 13:06 ` Rick Frankel
2012-01-27 13:56 ` Nicolas Goaziou
2012-01-27 16:31 ` Achim Gratz
2012-02-01 6:44 ` Achim Gratz
2012-01-26 20:10 ` Thomas S. Dye
2012-02-01 8:36 ` Jambunathan K
2012-01-27 8:10 ` Jambunathan K
2012-01-27 13:59 ` Nicolas Goaziou
2012-01-27 15:50 ` Bastien
2012-01-27 16:29 ` Thomas S. Dye
2012-01-27 17:04 ` Jambunathan K
2012-01-27 18:13 ` Thomas S. Dye
2012-01-27 18:31 ` Jambunathan K
2012-01-27 19:21 ` Achim Gratz
2012-01-27 19:48 ` Thomas S. Dye
2012-01-27 20:10 ` Nick Dokos
2012-01-27 20:11 ` Thomas S. Dye
2012-01-23 21:33 ` Thomas S. Dye
2012-01-22 19:21 ` Thomas S. Dye
2012-01-22 20:50 ` Nicolas Goaziou
2012-01-23 6:14 ` Thomas S. Dye
2012-01-23 7:03 ` Nicolas Goaziou
2012-01-23 15:53 ` Thomas S. Dye
2012-01-23 18:18 ` Nicolas Goaziou
2012-01-23 21:27 ` Thomas S. Dye
2012-01-23 12:20 ` Andreas Leha
2012-01-27 17:00 ` Thomas S. Dye
2012-02-03 22:57 ` Nicolas Goaziou
2012-02-04 16:42 ` Thomas S. Dye
2012-02-05 2:19 ` Thomas S. Dye
2012-02-05 2:58 ` Thomas S. Dye
2012-02-05 14:09 ` Nicolas Goaziou
2012-02-06 1:34 ` Thomas S. Dye
2012-02-06 14:29 ` Nicolas Goaziou
2012-02-06 16:39 ` Thomas S. Dye
2012-02-06 17:05 ` Nicolas Goaziou
2012-02-06 18:46 ` Thomas S. Dye
2012-02-07 7:27 ` Nicolas Goaziou
2012-02-07 8:57 ` Document date and last updated date Sebastien Vauban
2012-02-07 17:45 ` Nicolas Goaziou
2012-02-07 22:29 ` Sebastien Vauban
2012-02-07 6:22 ` [ANN] ASCII back-end for new export engine Thomas S. Dye
2012-02-07 7:07 ` Nicolas Goaziou
2012-02-07 9:00 ` Sebastien Vauban
2012-02-07 17:49 ` Nicolas Goaziou
2012-02-08 7:11 ` Jambunathan K
2012-02-07 15:45 ` Thomas S. Dye
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=87obtvk6j0.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).