From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <n.goaziou@gmail.com>
Subject: Re: Superscripts and subscripts
Date: Sat, 20 Apr 2013 21:19:47 +0200
Message-ID: <87d2tpko18.fsf@gmail.com>
References: <m14nf7bj0i.fsf@poto.westell.com> <87d2tv3s5b.fsf@bzg.ath.cx>
	<87k3nynzzv.fsf@gmail.com> <877gjy9wvg.fsf@Rainer.invalid>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:57596)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1UTdKD-0001SH-J4
	for emacs-orgmode@gnu.org; Sat, 20 Apr 2013 15:19:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1UTdKB-0006nb-1V
	for emacs-orgmode@gnu.org; Sat, 20 Apr 2013 15:19:53 -0400
Received: from mail-we0-x231.google.com ([2a00:1450:400c:c03::231]:38149)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <n.goaziou@gmail.com>) id 1UTdKA-0006nP-RF
	for emacs-orgmode@gnu.org; Sat, 20 Apr 2013 15:19:50 -0400
Received: by mail-we0-f177.google.com with SMTP id o7so4702046wea.8
	for <emacs-orgmode@gnu.org>; Sat, 20 Apr 2013 12:19:50 -0700 (PDT)
In-Reply-To: <877gjy9wvg.fsf@Rainer.invalid> (Achim Gratz's message of "Fri,
	19 Apr 2013 20:52:03 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org

Hello,

Achim Gratz <Stromeko@nexgo.de> writes:

> Nicolas Goaziou writes:
>> Of course, we could work around this with a new rule saying "the longest
>> match wins", which, in this case, is the underline. But it would be
>> better to find a more elegant solution, one which would remove the sole
>> ambiguity, AFAICT, in Org syntax.
>>
>> Suggestions welcome.
>
> How about {}^{14}C or {^{14}}C?

It means that a white space before a sub/superscript marker is invalid.
In that case, we can also use "\nbsp" entity instead of {}. It's longer,
but more standard.

Another option would be to change syntax for underline, doubling the
underscore characters:

  __underline__

The other advantage is that it may be less ambiguous if we ever allow
text markup within words.


Regards,

-- 
Nicolas Goaziou