From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ulf Stegemann Subject: Org Entities (was: Add \EUR to `org-html-entities') Date: Thu, 17 Dec 2009 10:04:18 +0100 Message-ID: References: <72EE83CC-7BA4-4AE2-84C3-2AF566C9CE37@gmail.com> <4B29781A-D02A-45CE-BF6F-998FCCF56A05@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NLCI4-0003uQ-UK for emacs-orgmode@gnu.org; Thu, 17 Dec 2009 04:04:57 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NLCI0-0003ta-2r for emacs-orgmode@gnu.org; Thu, 17 Dec 2009 04:04:56 -0500 Received: from [199.232.76.173] (port=38098 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NLCHz-0003tX-Ul for emacs-orgmode@gnu.org; Thu, 17 Dec 2009 04:04:51 -0500 Received: from lo.gmane.org ([80.91.229.12]:50218) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NLCHz-0000pT-CN for emacs-orgmode@gnu.org; Thu, 17 Dec 2009 04:04:51 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NLCHw-0003rE-0x for emacs-orgmode@gnu.org; Thu, 17 Dec 2009 10:04:48 +0100 Received: from london.zeitform.net ([146.140.213.100]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 17 Dec 2009 10:04:48 +0100 Received: from ulf-news by london.zeitform.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 17 Dec 2009 10:04:48 +0100 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: emacs-orgmode@gnu.org Hi Carsten, Carsten Dominik wrote: > I have added your symbols. thanks, works great. I was wondering if there's a more general problem lurking behind this (thus the change of subject): the problem of encoding entities in org for various export formats, namely HTML, LaTeX, plain ASCII text (and maybe plain unicode text). As an example, let's assume we have an org file that should eventually be available as HTML, PDF and plain text. Let's assume further, that for whatever reasons (e.g. ugly double quotes in the needed font) the document should use French quoting. Ideally `\SomeMagicOrgEncoding{}Quote\AnotherMagicOrgEncoding{}' in the org file would export to HTML -> «Quote» LaTeX -> \flqq{}Quote\frqq{} ASCII -> "Quote" (Unicode -> «Quote») Resorting to `org-html-entities' we could use --8<--------------------------snip-------------------------->8--- #+LATEX_HEADER: \newcommand{\laquo}{\flqq} \newcommand{\raquo}{\frqq} [...] \laquo{}Quote\raquo{} --8<--------------------------snap-------------------------->8--- to get the HTML and LaTeX output right but this leaves us with `\laquo{}' in ASCII export and is generally a rather cumbersome approach. Maybe there's a simpler solution to address this but I haven't come across it, yet (Note that `Use unicode!' isn't an option sometimes.). Quoting is just one example that strikes my quite often, but the same applies for all sorts of special characters; think of arrows, accented characters etc. This is certainly not a very pressing issue but it might be worth thinking about how to handle this. What do you think? Ulf