emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Florian Beck <fb@fbeck.net>
Cc: Florian Beck <fb@miszellen.de>, emacs-orgmode@gnu.org
Subject: Re: org-latex-classes with functions, incomplete doc
Date: Sun, 10 Feb 2013 22:52:11 +0100	[thread overview]
Message-ID: <87liavet10.fsf@gmail.com> (raw)
In-Reply-To: <87halkq9kq.fsf@sophokles.streitblatt.de> (Florian Beck's message of "Sun, 10 Feb 2013 19:59:17 +0100")

Florian Beck <fb@fbeck.net> writes:

> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>
>>> 	 (toc-title (if (plist-get info :toc-title)
>>> 			(org-element-property :toc-title headline)))
>>
>> There's no :toc-title property in the communication channel. The
>> exhaustive list of its properties is written in ox.el, at "The
>> Communication Channel" section.
>
> Obviouly, I defined it, otherwise it wouldn't work.
>
>   :options-alist ((:toc-title "TOC_TITLE" nil nil t) ... )
>
>>> As you can see, the solution is much more convoluted.
>>
>> Because you're not using the proper tool. If you just want to modify the
>> string returned by the `latex' back-end, use a filter. You will have
>> access to the transcoded headline (in LaTeX format, as a string) and the
>> communication channel.
>
> But not to the element properties, which is what I need.
>
>> There are already many ways to alter output from a back-end. It's just
>> a matter of using the right tool.
>
> So, which is it? I'm a bit confused right now.

I now get what you intend to do (or so I think).

I didn't implement this feature in ox-latex.el, mainly because a proper
implementation needs to be done at the ox.el level.

Anyway, we're back to step one: if you want to handle headlines
differently (i.e. by adding your own properties), you need to fork
`latex' back-end, as explained before. If you encounter problems, you
can post back here.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2013-02-10 21:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10 16:09 org-latex-classes with functions, incomplete doc Florian Beck
2013-02-10 17:06 ` Nicolas Goaziou
2013-02-10 17:51   ` Florian Beck
2013-02-10 18:20     ` Nicolas Goaziou
2013-02-10 18:59       ` Florian Beck
2013-02-10 21:52         ` Nicolas Goaziou [this message]
2013-02-12 23:27           ` Modifying the exporter (was: org-latex-classes with functions, incomplete doc) Florian Beck
2013-02-13 14:03             ` Modifying the exporter Nicolas Goaziou

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=87liavet10.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fb@fbeck.net \
    --cc=fb@miszellen.de \
    /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

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).