From mboxrd@z Thu Jan 1 00:00:00 1970 From: Diego Zamboni Subject: Re: Paragraph consisting only of number and full stop disappears in export Date: Mon, 5 Mar 2018 16:02:06 +0100 Message-ID: References: <87y3j7trzu.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a113d1bde10d7e50566ab9c7f" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34277) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1esrd2-0001cQ-D7 for emacs-orgmode@gnu.org; Mon, 05 Mar 2018 10:02:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1esrcw-0001bf-Jg for emacs-orgmode@gnu.org; Mon, 05 Mar 2018 10:02:16 -0500 Received: from mail-ot0-x22c.google.com ([2607:f8b0:4003:c0f::22c]:38926) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1esrcv-0001ZK-UL for emacs-orgmode@gnu.org; Mon, 05 Mar 2018 10:02:10 -0500 Received: by mail-ot0-x22c.google.com with SMTP id h8so15155003oti.6 for ; Mon, 05 Mar 2018 07:02:08 -0800 (PST) In-Reply-To: <87y3j7trzu.fsf@ericabrahamsen.net> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Eric Abrahamsen Cc: Org-mode --001a113d1bde10d7e50566ab9c7f Content-Type: text/plain; charset="UTF-8" Hi Eric, I found out that adding any non-space character after the dot prevents org from interpreting it as a list. In particular, adding a non-breaking-space entity at the end of the line works, like this: "300.\nbsp" Maybe other punctuations would also work and make sense in the context of your document- see `org-entities-help` for the full list of available entities. --Diego On Sun, Mar 4, 2018 at 11:07 PM, Eric Abrahamsen wrote: > Hi, > > I just discovered that a paragraph disappeared from a subtree I was > exporting, I guess because the paragraph consists of just a number > followed by a full stop, and was interpreted as a list item. I'm > translating subtitles, and the dialogue went: > > #+begin_src org > There are no taxis, but I've got a car. > > How much to Dongying? > > 300. > > We can be there 10am tomorrow. > #+end_src > > I'm not surprised that "300." got interpreted as a list item, but I > wonder if there's a way to protect against it being removed altogether. > I suppose it might be nice if a single list item with no content would > be interpreted as a paragraph, but that probably opens the door to all > kinds of weird edge cases. If there were just a way to escape it... > > Thanks, > Eric > > > --001a113d1bde10d7e50566ab9c7f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Eric,

I found out that adding any no= n-space character after the dot prevents org from interpreting it as a list= . In particular, adding a non-breaking-space entity at the end of the line = works, like this: "300.\nbsp"

Maybe othe= r punctuations would also work and make sense in the context of your docume= nt- see `org-entities-help` for the full list of available entities.
<= div>
--Diego


On Sun, Mar 4, 2018 at 11:07 PM, Eric A= brahamsen <eric@ericabrahamsen.net> wrote:
Hi,

I just discovered that a paragraph disappeared from a subtree I was
exporting, I guess because the paragraph consists of just a number
followed by a full stop, and was interpreted as a list item. I'm
translating subtitles, and the dialogue went:

#+begin_src org
There are no taxis, but I've got a car.

How much to Dongying?

300.

We can be there 10am tomorrow.
#+end_src

I'm not surprised that "300." got interpreted as a list item,= but I
wonder if there's a way to protect against it being removed altogether.=
I suppose it might be nice if a single list item with no content would
be interpreted as a paragraph, but that probably opens the door to all
kinds of weird edge cases. If there were just a way to escape it...

Thanks,
Eric



--001a113d1bde10d7e50566ab9c7f--