From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Org Entities (was: Add \EUR to `org-html-entities') Date: Thu, 17 Dec 2009 13:49:46 +0100 Message-ID: References: <72EE83CC-7BA4-4AE2-84C3-2AF566C9CE37@gmail.com> <4B29781A-D02A-45CE-BF6F-998FCCF56A05@gmail.com> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NLFo9-0004e0-Sg for emacs-orgmode@gnu.org; Thu, 17 Dec 2009 07:50:18 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NLFo5-0004cp-Hd for emacs-orgmode@gnu.org; Thu, 17 Dec 2009 07:50:17 -0500 Received: from [199.232.76.173] (port=35837 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NLFo5-0004cg-57 for emacs-orgmode@gnu.org; Thu, 17 Dec 2009 07:50:13 -0500 Received: from mail-ew0-f224.google.com ([209.85.219.224]:48366) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NLFnv-0001QQ-7z for emacs-orgmode@gnu.org; Thu, 17 Dec 2009 07:50:12 -0500 Received: by ewy24 with SMTP id 24so2218779ewy.26 for ; Thu, 17 Dec 2009 04:49:49 -0800 (PST) In-Reply-To: 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: Ulf Stegemann Cc: emacs-orgmode@gnu.org Hi Ulf, feel free to send me a modified version of the definitions of org-html-entities which contains an ASCII element as the third element of a list. I would then use this element for ASCII export. - Carsten On Dec 17, 2009, at 10:04 AM, Ulf Stegemann wrote: > 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 =20= > 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 =20= > file > would export to > > HTML -> «Quote» > LaTeX -> \flqq{}Quote\frqq{} > ASCII -> "Quote" > (Unicode -> =ABQuote=BB) > > 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 > > > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten