all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: christian.moe@hf.uio.no
Cc: Emacs-orgmode@gnu.org
Subject: Re: Newbie: Custom link type formatting in LaTeX export?
Date: Wed, 12 May 2010 08:15:33 +0200	[thread overview]
Message-ID: <3D145F75-7633-4F98-A7CD-1300228A42FE@gmail.com> (raw)
In-Reply-To: <4BE92DCB.1070408@hf.uio.no>


On May 11, 2010, at 12:13 PM, Christian Moe wrote:

> Hi,
>
> (I'm new to the list; have been an enthusiastic Org user for a year  
> and
> half; now using version 6.36; am an Elisp novice.)
>
> It looks like support for formatting custom link types in LaTeX export
> is broken?
>
> I was trying to implement a custom link type with its own formatting
> function for HTML and LaTeX export, following the steps in
> org-bbdb.el.
>
> I've found that org-bbdb-export does not italicize bbdb links in
> LaTeX, nor does my own org-cite-export turn my custom =cite:= links
> into LaTeX =\cite{}= citations. Everything works fine in HTML export,
> but in LaTeX all custom link types get formatted as =\texttt{descr}=.
>
> I see that org-export-as-html and org-export-as-docbook look up
> org-link-protocols to get the function for formatting the link, but it
> seems that org-export-as-latex doesn't.

Hi CHristian,

this is correct.  Since you already looked into the code, would you  
like to write a patch to this effect?

- Carsten

  reply	other threads:[~2010-05-12  6:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 10:13 Newbie: Custom link type formatting in LaTeX export? Christian Moe
2010-05-12  6:15 ` Carsten Dominik [this message]
2010-05-12 10:12   ` Christian Moe
2010-05-12 13:15     ` Carsten Dominik
2010-05-12 18:19       ` Christian Moe
2010-05-12 18:28       ` Christian Moe

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D145F75-7633-4F98-A7CD-1300228A42FE@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=Emacs-orgmode@gnu.org \
    --cc=christian.moe@hf.uio.no \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.