From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel Clemente" Subject: Re: XHTML export -   etc. Date: Fri, 2 Nov 2007 21:20:03 +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> 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 1Io2zu-0002nM-Om for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 16:20:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Io2zt-0002n6-AC for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 16:20:06 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Io2zt-0002n3-5Y for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 16:20:05 -0400 Received: from mu-out-0910.google.com ([209.85.134.186]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Io2zs-0000u6-PZ for emacs-orgmode@gnu.org; Fri, 02 Nov 2007 16:20:04 -0400 Received: by mu-out-0910.google.com with SMTP id i2so1354367mue for ; Fri, 02 Nov 2007 13:20:03 -0700 (PDT) In-Reply-To: <41c818190711021150w49e8fbbdu5258300bae65f736@mail.gmail.com> 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: William Henney Cc: emacs-orgmode@gnu.org > Shouldn't they be `&endash;' and `&emdash;' in HTML? > > http://www.w3.org/TR/xhtml1/dtds.html#a_dtd_Symbols > You mean – and — – and — for -- and --- respectively is ok. I think there exist no ---- and ----- ­ with \- and   with ~ are also good... There exists also ​ (zero-width space), but that's not a sign for breaking words into syllables; ­ is in addition better implemented. That means that following signs: \- ~ -- --- would have a special meaning when being exported on all org documents. I don't know if ~ is a good election. It should be looked for inside of words (li~ke this), but probably excluding URLs. Maybe that causes more problems to the users who want to write a literal ~. 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. Greets, Daniel