emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: LaTeX export problem
Date: Wed, 16 Jul 2014 16:36:16 +0200	[thread overview]
Message-ID: <8738e1jrq7.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2tx6lq7cu.fsf@tsdye.com> (Thomas S. Dye's message of "Sun, 13 Jul 2014 11:25:21 -1000")

Hello,

tsd@tsdye.com (Thomas S. Dye) writes:

> With a recent Org from git and this source:
>
>   #+attr_latex: :width 0.8\textwidth :placement [htb]
>   #+name: fig:harris-errors
>   #+caption[Structural effects of false transitives]: Structural effects of false transitives with the stratigraphic section in Figure [[fig:fig12-open]]:

> I get this incorrect LaTeX output:

[...]

> If I place a space between the final colon and the link on the
> first #+caption: line, then I get the output I'm expecting (although
> there is the extraneous space):

[...]


This is because regexp finding short captions is greedy. It thus catches
everything up to the last "]:" in the first line, making the link
invalid.

> Is there a work-around?

Just make sure the line containing the short caption doesn't end with
"]:", e.g.,

  ...
  #+caption[Structural effects of false transitives]:
  #+caption: Structural effects of false transitives with the stratigraphic section in Figure [[fig:fig12-open]]:
  ...


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2014-07-16 14:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 21:25 LaTeX export problem Thomas S. Dye
2014-07-16 14:36 ` Nicolas Goaziou [this message]
2014-07-16 16:35   ` Thomas S. Dye
  -- strict thread matches above, loose matches on Subject: below --
2012-09-12 16:47 Gary Oberbrunner
2012-09-19  7:57 ` Bastien
2012-09-20 14:59   ` Alexander Vorobiev
2012-09-21  8:48     ` Bastien
2012-09-21 19:47       ` Alexander Vorobiev
2012-09-21 21:21         ` Thomas S. Dye
2012-09-22  8:01           ` Nicolas Goaziou
2012-09-22  8:07         ` Nicolas Goaziou
2012-09-24 16:40           ` Alexander Vorobiev
2012-09-24 21:15             ` Nicolas Goaziou
2012-09-24 21:32               ` Alexander Vorobiev
2012-09-26 18:48                 ` Nicolas Goaziou
2012-01-09 15:45 Piotr Kaźmierczak
2012-01-10  0:13 ` Nick Dokos
2012-01-17 13:35   ` Piotr Kaźmierczak
2012-01-17 17:00     ` Nick Dokos
2012-01-17 19:00       ` Piotr Kaźmierczak
2012-01-17 20:45     ` Eric S Fraga
2010-09-30 14:55 latex " Jörg Hagmann
     [not found] ` <4CA4C29B.1060404@christianmoe.com>
2010-10-01  7:30   ` Jörg Hagmann
2010-10-01  7:32 ` Noorul Islam K M
2010-10-01  7:40   ` Jörg Hagmann
2010-10-01  9:03     ` Noorul Islam K M
2010-10-01  9:17       ` Noorul Islam
2010-10-01 11:38         ` Jörg Hagmann
2010-10-01 12:05           ` Jörg Hagmann

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=8738e1jrq7.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.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).