From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel Clemente" Subject: Re: XHTML export -   etc. Date: Wed, 7 Nov 2007 17:09:43 +0100 Message-ID: References: <20071102121343.GD31416@atlantic.linksys.moosehall> <87d4usbrdw.fsf@bzg.ath.cx> <20071102151934.GA13544@atlantic.linksys.moosehall> <871wb85u8j.fsf@bzg.ath.cx> <41c818190711021150w49e8fbbdu5258300bae65f736@mail.gmail.com> <87sl3oxkep.fsf@bzg.ath.cx> <87y7de9o23.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IpnTQ-0000pF-Rl for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 11:09:48 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IpnTO-0000p0-Pb for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 11:09:47 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IpnTO-0000ox-ME for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 11:09:46 -0500 Received: from mu-out-0910.google.com ([209.85.134.191]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IpnTO-0003rd-EH for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 11:09:46 -0500 Received: by mu-out-0910.google.com with SMTP id i2so4130281mue for ; Wed, 07 Nov 2007 08:09:44 -0800 (PST) In-Reply-To: <87y7de9o23.fsf@bzg.ath.cx> Content-Disposition: inline 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: Bastien Cc: emacs-orgmode@gnu.org Hi > > By "nonbreaking character", I meant the output of C-x 8 SPC (try it). > > This is iso-8859-1, not ascii, so we should avoid to handle this in Org > source file -- but my bet is that people who want to insert nonbreaking > characters are also people using other charsets than ascii. > If you use C-x 8 SPC in a text file, you probably want to export it as ~ in LaTeX, not to include that Unicode character directly. But this conversion is a strange one, therefore it may be besser to offer a syntax for the ~ (non-breaking space) in LaTeX. For instance \~ or ~ > > Is it better to enter the unicode character directly, or offering > > something like \~ ? > > For me \~ would rather mean "don't convert ~", which means: output "~" > (at least in LaTeX, since the normal LaTeX conversion for ~ is \~) > But we said that if someone writes ~ in an org-file, then it is expected that ~ appears at the result. Therefore: ~ is for the sign ~ other sign (maybe \~ ) is for the non-breaking space I know this behaviour it's not the same as LaTeX, but I don't think it's a problem. Daniel