emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [ANN] ASCII back-end for new export engine
Date: Thu, 26 Jan 2012 03:59:40 -1000	[thread overview]
Message-ID: <m1ty3i36pf.fsf@tsdye.com> (raw)
In-Reply-To: <87obtrel2z.fsf@gmail.com> (Nicolas Goaziou's message of "Wed, 25 Jan 2012 18:41:24 +0100")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> I think that your understanding of the new exporter architecture is
>> intimate and secure.  I'm happy to follow your lead here.
>
> I know for sure my way around the new exporter, but my LaTeX skills
> aren't on par with that knowledge.
>
> Anyway, I've pushed a commit which tries to create smart links.
>
> Basically, links without a description pointing to an headline will be
> turned into \ref{headline-label}, unless headline's numbering is off, in
> which case they become \hyperref[headline-label]{headline-title}.
>
> Nothing is changed for links providing their own description, and links
> not pointing to headlines.
>
> That should remove the need for a variable.
>
> What do you think about it?
>

Yes, this seems to work nicely.  Thanks!

You mentioned unnumbered headlines.  I wonder, would it be possible (or
useful) to have the num: option take an integer (like toc:)?  As I
understand it now, its value is either nil or not nil.  It doesn't
manipulate \secnumdepth, but instead uses \section*, etc.  In LaTeX,
section* means not only that the section isn't numbered, but also that
it doesn't go into the table of contents.  There are many times when it
is useful to put unnumbered sections in the table of contents.

I've been doing #+LaTeX_HEADER: \setcounter{secnumdepth}{1}, and this
works fine.  However, it would be nicer to do num: 1.

A way to set individual headings as numbered or unnumbered would be
deluxe.  Perhaps this is possible, but I haven't found it?


>> It looks like a terrific example of the power of your parser.
>
> No, its (albeit useless) power is revealed by the fact that "\n:t" is
> now supported in LaTeX (and ASCII). Such a feat was close to impossible
> with the previous engine.
>
> More seriously, being recursive, the new engine can export thinks like
> "some *text /with nested/ emphasis*" and even "*/important/*".
>

It looks like there will need to be many changes to the documentation.

> And, more importantly, it is mostly made of independent parts, for
> easier maintenance. For example, if I want to fix or improve links in
> e-latex back-end, I know I have to start diving in
> `org-e-latex-link'. That function may call other internal functions,
> but, at least, I have a starting point. That will also be true for any
> other back-end to come.
>
>
> Regards,

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

  parent reply	other threads:[~2012-01-26 13:59 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
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 [this message]
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=m1ty3i36pf.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.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).