From mboxrd@z Thu Jan  1 00:00:00 1970
From: tsd@tsdye.com (Thomas S. Dye)
Subject: Re: [ANN] ASCII back-end for new export engine
Date: Sun, 22 Jan 2012 20:14:57 -1000
Message-ID: <m1hazn2bdq.fsf@tsdye.com>
References: <87pqec4xua.fsf@gmail.com> <m1wr8j35ng.fsf@tsdye.com>
	<87bopvjwce.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([140.186.70.92]:37697)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tsd@tsdye.com>) id 1RpDB8-0008CB-93
	for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 01:14:55 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <tsd@tsdye.com>) id 1RpDB6-0005je-NY
	for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 01:14:54 -0500
Received: from oproxy8-pub.bluehost.com ([69.89.22.20]:41162)
	by eggs.gnu.org with smtp (Exim 4.71) (envelope-from <tsd@tsdye.com>)
	id 1RpDB6-0005jG-Cl
	for emacs-orgmode@gnu.org; Mon, 23 Jan 2012 01:14:52 -0500
In-Reply-To: <87bopvjwce.fsf@gmail.com> (Nicolas Goaziou's message of "Sun, 22
	Jan 2012 21:50:09 +0100")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>

Aloha Nicolas,

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

> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> I think there might be a problem with the regular expression for
>> captions on line 703 or org-e-latex.el.  I have a dim understanding of
>> regular expressions and the various parsers, but I suspect the problem
>> is in this part: [^][]. 
>>
>> At any rate, this input:
>> #+CAPTION: [An example photograph]{An example photograph}.
>> #+LABEL: fig:photo
>
> The regexp isn't the problem here. But this all means that I'm breaking
> a golden rule: never parse something already parsed.
>
> Anyway, I have switched caption keyword to the dual keywords
> category. That means is syntax is now like results keywords' which can
> have an optional string (a hash in this case) before their main value.
>
> To put it simply, caption syntax can now be:
>
>                           #+caption: long name
>                          #+caption[]: long name
>                     #+caption[short name]: long name
>
> much like
>
>                          #+results[hash]: name
>
> Though,
>
>                          #+caption[something]:
>
> is equivalent to no caption since the main value is mandatory.

This input:

#+CAPTION[An example photograph]: An example photograph.
#+NAME: fig:photo

for me, yields:

\caption{\label{fig:photo}An example photograph}

I was expecting:

\caption[An example photograph]{\label{fig:photo}An example photograph}

>
> As a side note, #+label has been deprecated in favor of #+name (though
> the former is immediately translated into the latter at parse time).

I agree it is a good idea to abstract this from the LaTeX backend.

>
>
> Regards,

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com