From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel Clemente" Subject: Re: XHTML export -   etc. Date: Sun, 4 Nov 2007 01:00:08 +0100 Message-ID: References: <20071102121343.GD31416@atlantic.linksys.moosehall> <20071102122038.GF23492@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> 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 1IoSuT-0002Ne-0H for emacs-orgmode@gnu.org; Sat, 03 Nov 2007 20:00:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IoSuR-0002N5-Gc for emacs-orgmode@gnu.org; Sat, 03 Nov 2007 20:00:12 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IoSuR-0002N2-EE for emacs-orgmode@gnu.org; Sat, 03 Nov 2007 20:00:11 -0400 Received: from fk-out-0910.google.com ([209.85.128.186]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IoSuQ-0005NU-5D for emacs-orgmode@gnu.org; Sat, 03 Nov 2007 20:00:10 -0400 Received: by fk-out-0910.google.com with SMTP id 19so2298442fkr for ; Sat, 03 Nov 2007 17:00:08 -0700 (PDT) In-Reply-To: <87sl3oxkep.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 > > > The symbol for =84breaking allowed" could also be \~ ... That's an > > inconsistency with LaTeX ~, but is consistent with LaTeX's \- And > > that would leave ~ untouched and just use \- and \~ for hyphenation. > > What is wrong with \- ? It seems enough to me. Sorry, I wanted to say the symbol for =84*nonbreaking space*" could be \~ , instead of just ~ That way the symbols for hyphenation are more symmetrical: \- for =84breaking allowed" and \~ for =84nonbreaking space". And then the normal ~ is still rendered as expected. > I removed the idea of using the tilde character `~' for inerting a non= -breakable space in Org source file because: > ... > - this is the function of Emacs non-breakable space character `' What do you mean? Did you type something? I see nothing; just `' Is it better to enter the unicode character directly, or offering something like \~ ? I suppose both could be changed at the exporting, so maybe it's a matter of taste. Daniel