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: Mon, 06 Feb 2012 08:46:05 -1000
Message-ID: <m1haz3242a.fsf@tsdye.com>
References: <87pqec4xua.fsf@gmail.com> <m1vcnk2198.fsf@tsdye.com>
	<87zkcwt4qg.fsf@gmail.com> <m1liof29wr.fsf@tsdye.com>
	<87liofuc2k.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]:56354)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <tsd@tsdye.com>) id 1RuTZy-0004I2-Uv
	for emacs-orgmode@gnu.org; Mon, 06 Feb 2012 13:46:22 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <tsd@tsdye.com>) id 1RuTZu-0002oW-HI
	for emacs-orgmode@gnu.org; Mon, 06 Feb 2012 13:46:18 -0500
Received: from oproxy1-pub.bluehost.com ([66.147.249.253]:54612)
	by eggs.gnu.org with smtp (Exim 4.71) (envelope-from <tsd@tsdye.com>)
	id 1RuTZu-0002oD-Ad
	for emacs-orgmode@gnu.org; Mon, 06 Feb 2012 13:46:14 -0500
In-Reply-To: <87liofuc2k.fsf@gmail.com> (Nicolas Goaziou's message of "Mon, 06
	Feb 2012 18:05:39 +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>

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

> tsd@tsdye.com (Thomas S. Dye) writes:
>
>> The old exporter recognized LaTeX commands for accented characters.  So,
>> \=o in the Org mode file would yield \={o} in the LaTeX file.  The new
>> exporter gives $\backslash$=o for this construct.  
>
> Indeed, the parser recognizes LaTeX commands and environments, but is
> more strict with other LaTeXisms.
>
>> How does the new
>> LaTeX exporter recognize accented characters?
>
> The Org way (portable across major back-ends) to handle this is to
> define an new entity, and name it for example "omacr"[1]. You can
> then access it with \omacr in your buffer.

Yes, this seems like a good solution.  Thanks.
>
> Other (but inferior) solutions could be to define a macro:
>
>                           #+macro: omacr \={o}
>
> or use an export snippet:
>
>                             @e-latex{\={o}}
>
>> I can't find a way to get creator information into \hypersetup{} without
>> also having it inserted as normal text at the end of the file.  Is this
>> possible?
>
> That's not possible at the moment.
>
> There are three states for creator, on, off and comment, and two places
> to insert the information (in hypersetup and at the end of the exported
> data).
>
> What would be a correct way to handle the different configurations here?
>

Perhaps:

  - off, no information is inserted
  - on, information is inserted in \hypersetup{} and as text at the end of the file
  - comment, information is inserted in \hypersetup and as a comment at the
end of the file.
 
All the best,
Tom

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