emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: New exporter queries, captions
Date: Thu, 13 Sep 2012 06:57:02 -1000	[thread overview]
Message-ID: <m1pq5p7tep.fsf@poto.westell.com> (raw)
In-Reply-To: <87obl9sxkp.fsf@gmail.com> (Nicolas Goaziou's message of "Thu, 13 Sep 2012 18:21:26 +0200")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
> tsd@tsdye.com (Thomas S. Dye) writes:
>> Three queries about captions in the new exporter:
>> 1) The old exporter allowed a structure like this #+CAPTION: [Short
>> caption]{Long caption.} to export \caption[Short caption]{Long caption.}
>> to LaTeX.  The new exporter gives something like this \caption{[Short
>> caption]{Long caption.}}  Can the former behavior be implemented in the
>> new exporter?
> Correct syntax is:
>   #+CAPTION[short]: long
> much like:
>   #+RESULTS[hash]: name
Got it.  Thanks.
>> 2) Caption text appears to require markup in the export target language,
>> rather than org markup.  So, for LaTeX export I need something like
>> #+CAPTION: Things: \textit{a}, some; \textit{b}, other.  
>> Rather than, #+CAPTION: /a/, some; /b/, other.  Shouldn't caption text
>> honor org markup so it can be exported correctly to different backends?
>> Is there a switch for this?
> That was a bug. Captions honor Org syntax again. Thanks.

Is it possible to expand links, too?  If I have
#+CAPTION: Data from [[textcite:ladefoged08:_variab_hawaii][;]].
I get
\caption{Data from [[textcite:ladefoged08:_variab_hawaii][;]].}

My textcite link type is here:

#+name: define-biblatex-textcite-link
#+begin_src emacs-lisp :results silent :exports none
   "textcite" 'ebib
   (lambda (path desc format)
      ((eq format 'html)
       (format "(<cite>%s</cite>)" path))
      ((eq format 'latex)
       (if (or (not desc) (equal 0 (search "textcite:" desc)))
           (format "\\textcite{%s}" path)
         (format "\\textcite[%s][%s]{%s}"
                 (cadr (split-string desc ";"))
                 (car (split-string desc ";"))  path))))))

>> 3) My captions are often long.  Is it possible to enter these so they
>> aren't all on one line?  Something like
>> #+CAPTION: Line one
>> #+CAPTION: Line two
>> would be great.
> It is now implemented.

Terrific.  Thanks!

All the best,

T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884

  reply	other threads:[~2012-09-13 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 21:26 Thomas S. Dye
2012-09-13 16:21 ` Nicolas Goaziou
2012-09-13 16:57   ` Thomas S. Dye [this message]
2012-09-30 21:59     ` Nicolas Goaziou
2012-10-01  5:20       ` Thomas S. Dye

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:

  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=m1pq5p7tep.fsf@poto.westell.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \


* 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


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