From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Thomas Holst <thomas.holst@de.bosch.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [new exporter] Problems with entities
Date: Mon, 27 Aug 2012 11:33:26 +0200 [thread overview]
Message-ID: <876284adcp.fsf@gmail.com> (raw)
In-Reply-To: <ywodbohwsnvn@de.bosch.com> (Thomas Holst's message of "Mon, 27 Aug 2012 11:08:44 +0200")
Hello,
Thomas Holst <thomas.holst@de.bosch.com> writes:
> While testing the new exporter we encountered problems with entities. We
> tried to make ligations work. In LaTeX you write '\/' for a ligation
> e.g. 'f\/ifteen'. To achieve that we set `org-entities-user':
>
> #+BEGIN_SRC emacs-lisp
> (setq org-entities-user
> '("Ligatur" "\\/" nil "" "" "" ""))
> #+END_SRC
>
> The following text is used to show the problem:
>
> Dies ist eine Ligatur: f\/ifteen \alpha ab\-cd.
>
> With the old exporter the translation to LaTeX is:
>
> Dies ist eine Ligatur: f\/ifteen $\alpha$ ab\-cd.
>
> Which is the expected result. With the new exporter we get:
>
> Dies ist eine Ligatur: f$\backslash$/ifteen $\alpha$
> ab$\backslash$-cd.
>
> As you can see the shy hyphen is also wrong. But \alpha is exported
> correctly. So I don't know what is happening here.
You have defined an entity named "Ligatur". If you want to apply it
during export, you have to write either \Ligatur or \Ligatur{}. For
example, \alpha is correctly exported since there is:
("alpha" "\\alpha" t "α" "alpha" "alpha" "α")
in `org-entities'.
Note that old exporter doesn't apply your entity either (entities usage
doesn't change between both exporters). It just gives up each time he
sees a backslash which isn't followed by a known entity name, assuming
this will be handled by LaTeX.
HTH,
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-08-27 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 9:08 [new exporter] Problems with entities Thomas Holst
2012-08-27 9:33 ` Nicolas Goaziou [this message]
2012-08-27 10:02 ` Thomas Holst
2012-08-27 13:41 ` 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=876284adcp.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=thomas.holst@de.bosch.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).