From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Florian Beck <fb@miszellen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-latex-classes with functions, incomplete doc
Date: Sun, 10 Feb 2013 19:20:31 +0100 [thread overview]
Message-ID: <877gmgf2ts.fsf@gmail.com> (raw)
In-Reply-To: <87zjzcqcq8.fsf@sophokles.streitblatt.de> (Florian Beck's message of "Sun, 10 Feb 2013 18:51:11 +0100")
Florian Beck <fb@miszellen.de> writes:
> Ok, I tried this. There is a problem, however. This is what I came up
> with:
>
> #+BEGIN_SRC emacs-lisp
> (defun fb/org-latex-headline (headline contents info)
> (let* ((full-section (org-latex-headline headline contents info))
I suggest (org-export-with-backend 'latex headline contents info) to not
depend on the actual name of the translator.
> (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.
> (section-regex "\\`\\\\\\(sub\\)*\\(section\\|paragraph\\){")
> (new-section
> (when (and toc-title
> (string-match section-regex full-section))
> (let ((subs (match-string 1 full-section))
> (section (match-string 2 full-section))
> (rest (substring full-section (match-end 0))))
> (concat
> "\\" subs section "["
> ;; replace brackets (from `org-latex-headline')
> (replace-regexp-in-string
> "\\[" "("
> (replace-regexp-in-string
> "\\]" ")"
> toc-title))
> "]{" rest)))))
> (or new-section
> full-section)))
> #+END_SRC
>
> 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.
#+begin_src emacs-lisp
(defun fb/my-headline-transformation (headline backend info)
(when (eq backend 'latex)
;; Here HEADLINE is the output from `latex' back-end, as a string.
...
))
(add-to-list 'org-export-filter-headline-functions
'fb/my-headline-transformation)
#+end_src
What I suggest gives you access to the headline as parsed data. This is
much more powerful, but a completely different task.
> IMO, the probem is this: the translation is (mostly) application of
> content to a template (a format string), but these templates are build
> (mostly, sectioning is actually an exception) inside the default
> translation functions. It would be much easier, when this template would
> be accessible from "outside", like this:
There are already many ways to alter output from a back-end. It's just
a matter of using the right tool.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-02-10 18:20 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 [this message]
2013-02-10 18:59 ` Florian Beck
2013-02-10 21:52 ` Nicolas Goaziou
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=877gmgf2ts.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--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
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).