From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel Clemente" Subject: Re: XHTML export -   etc. Date: Wed, 7 Nov 2007 19:04:07 +0100 Message-ID: References: <20071102121343.GD31416@atlantic.linksys.moosehall> <871wb85u8j.fsf@bzg.ath.cx> <41c818190711021150w49e8fbbdu5258300bae65f736@mail.gmail.com> <87sl3oxkep.fsf@bzg.ath.cx> <87y7de9o23.fsf@bzg.ath.cx> <87mytqkl9q.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IppGC-0000iK-32 for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 13:04:16 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IppG8-0000cB-Fd for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 13:04:15 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IppG8-0000bp-2L for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 13:04:12 -0500 Received: from fk-out-0910.google.com ([209.85.128.185]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IppG8-0005wN-0B for emacs-orgmode@gnu.org; Wed, 07 Nov 2007 13:04:12 -0500 Received: by fk-out-0910.google.com with SMTP id 19so4590822fkr for ; Wed, 07 Nov 2007 10:04:10 -0800 (PST) In-Reply-To: <87mytqkl9q.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 > > > 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. > > This is what i suggested. > Ok, I misunderstood because you said =84so we should avoid to handle this in Org source file" > > But this conversion is a strange one, > > Why? Well, I didn't know the character inserted by C-x 8 SPC, and I suppose most people don't use it frequently. However, it could be used and that would be simple. For instance: - you write C-x 8 SPC in your org files - C-x 8 SPC is exported to   on HTML - C-x 8 SPC is exported to ~ on HTML - ~ continues working normally: produces ~ on HTML and \~{} on LaTeX > > > therefore it may be besser to offer a syntax for the ~ (non-breaking > > space) in LaTeX. For instance \~ or ~ > > I think I misunderstood at some point. For me "\~" means "protect the > tilde character from conversion" which means "don't escape the tilde", > which results into a LaTeX nonbreaking-space (~). > But we don't need to =84protect the tilde from conversion" because ~ already writes the tilde unconverted. \~ is still free to other uses. Sometimes the \ means =84don't escape", sometimes not. For instance at \- it wouldn't mean =84insert a hyphen", but =84breaking allowed". Yes, that's confusing... Daniel