emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [patch, ox-latex] better hyperref and title options
Date: Sun, 15 Feb 2015 12:42:16 +0100	[thread overview]
Message-ID: <874mqn765j.fsf@gmx.us> (raw)
In-Reply-To: <878ufzo3f2.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 15 Feb 2015 11:49:21 +0100")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:


>> However, since they are plain strings something like \alpha will be
>> exported as $\backslash$lpha.  I can kind of get it interpreting using
>> org-element-parse-secondary-string, but this is not the right
>> approach.
>
> Why isn't it the right approach?

'Cause usually org-export-data gives you the right value automatically.
Anyway, I don't mind using  org-element-parse-secondary-string.

>> Is there a reason why DESCRIPTION and KEYWORDS can't have formatting?
>
> DESCRIPTION could be moved to `org-element-document-properties'. But
> then, we need to introduce `org-export-with-description', which implies
> export back-ends have to deal with it somehow (ATM "ox-ascii" ignores
> it).

> Another option is to simply remove DESCRIPTION from "ox.el" and let
> export back-ends in need of it to add it to their definition.

I don't oppose that.

> However, I don't see why KEYWORDS should accept markup. I also think it
> should be moved to back-end definitions instead of "ox.el".

Keywords should also be printed in the document as well IMO, e.g. after
the abstract.  An example of where you need markup: σ-algebra.

—Rasmus

-- 
Slowly unravels in a ball of yarn and the devil collects it

  reply	other threads:[~2015-02-15 11:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-12  0:39 [patch, ox-latex] better hyperref and title options Rasmus
2015-02-12 23:59 ` Nicolas Goaziou
2015-02-15  1:53   ` Rasmus
2015-02-15 10:49     ` Nicolas Goaziou
2015-02-15 11:42       ` Rasmus [this message]
2015-02-15 12:57         ` Nicolas Goaziou
2015-02-15 13:11           ` Rasmus
2015-02-15 15:57             ` Nicolas Goaziou
2015-02-15 16:55               ` Rasmus
2015-02-19  1:26           ` Rasmus
2015-02-19  9:24             ` Nicolas Goaziou
2015-02-19 21:43               ` Rasmus
2015-02-19 22:58                 ` 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=874mqn765j.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --cc=emacs-orgmode@gnu.org \
    /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).