From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Insert ampersand in HTML export? Date: Sun, 13 Feb 2011 10:10:13 +0100 Message-ID: <87aai0pafe.fsf@gnu.org> References: <20110210152542.26383056amscopub-mail@yahoo.com@dove.localdomain> <20110211114831.2a53a9ffamscopub-mail@yahoo.com@dove.localdomain> <874o89tmwf.fsf@altern.org> <8623B408-3E2C-4BC2-BF7B-179A7C295A17@gmail.com> <871v3dp97c.fsf@gnu.org> <20110212155103.16e82a76uriavalos@yahoo.com@dove.localdomain> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=60185 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PoXy4-0007S4-T1 for emacs-orgmode@gnu.org; Sun, 13 Feb 2011 04:10:09 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PoXy4-0001yc-0j for emacs-orgmode@gnu.org; Sun, 13 Feb 2011 04:10:08 -0500 Received: from mail-bw0-f41.google.com ([209.85.214.41]:42127) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PoXy3-0001yX-Pa for emacs-orgmode@gnu.org; Sun, 13 Feb 2011 04:10:07 -0500 Received: by bwz16 with SMTP id 16so4522686bwz.0 for ; Sun, 13 Feb 2011 01:10:06 -0800 (PST) In-Reply-To: <20110212155103.16e82a76uriavalos@yahoo.com@dove.localdomain> (Uriel Avalos's message of "Sat, 12 Feb 2011 15:51:03 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Uriel Avalos Cc: emacs-orgmode@gnu.org Hi Uriel, Uriel Avalos writes: > What about some type of escape character like \&? That way \& is > exported as & instead of & or \$. Would that work? Handling escape characters is quite tricky, I'd better not go that way. > org-export-html-protect-char-alist may work in my case---the MATHML > macros are in a seperate #+SETUPFILE. As long as this variable doesn't > "bubble up" i.e., apply to the file that calls #+SETUPFILE, then it > will work. Please tell me if it works. Thanks! -- Bastien