From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Re: Future Worg publishing failure :) Date: Fri, 18 Mar 2011 10:34:19 -0400 Message-ID: <27408.1300458859@alphaville.dokosmarshall.org> References: <15689.1300433701@alphaville.dokosmarshall.org> <87y64cg2n5.fsf@gnu.org> <874o708usn.fsf@gmail.com> Reply-To: nicholas.dokos@hp.com Return-path: Received: from [140.186.70.92] (port=36470 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q0alC-0001Nc-29 for emacs-orgmode@gnu.org; Fri, 18 Mar 2011 10:34:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q0al8-0006Oq-Ke for emacs-orgmode@gnu.org; Fri, 18 Mar 2011 10:34:36 -0400 Received: from vms173003pub.verizon.net ([206.46.173.3]:53728) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q0al8-0006OH-HS for emacs-orgmode@gnu.org; Fri, 18 Mar 2011 10:34:34 -0400 Received: from alphaville.dokosmarshall.org ([unknown] [173.76.32.106]) by vms173003.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LI900D0WCH7M360@vms173003.mailsrvcs.net> for emacs-orgmode@gnu.org; Fri, 18 Mar 2011 09:34:20 -0500 (CDT) In-reply-to: Message from Nicolas of "Fri, 18 Mar 2011 13:42:00 BST." <874o708usn.fsf@gmail.com> 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: Nicolas Cc: Bastien , nicholas.dokos@hp.com, emacs-orgmode@gnu.org Nicolas wrote: > Hello, > > Bastien writes: > > >> Current org code takes the 14. as an item in a numbered list. When > >> exporting to HTML, this causes an error in org-html-export-list-line - > >> hence the subject line. It's not a problem right now but it will be when > >> orgmode.org gets the updated version. I reformatted the line to avoid > >> the awkward newline, so the future publishing failure will not > >> happen. > > > > Thanks for that! > > > >> I'll let Nicolas worry about what should be done about the error. > > > > Let's not leave Nicolas alone here :) I'll take a look myself into it > > over the week-end. > By the time I find my way through the code, Nicolas will have solved it 10 times over. > Phew, what a relief ;) > > The only solution I could think of is somewhere in the patchwork server > ("Auto-fill shouldn't insert new items"). > Are you saying that the patchwork server introduced this? Or that the patchwork server should solve it? In the case I stumbled upon (a Worg file), the patchwork server is nowhere in sight, I think: the change was (I'm guessing here) directly committed, so maybe the original writer had auto-fill turned on, but maybe not and just typed it that way. So neither the patchwork server nor making auto-fill smarter would provide a guaranteed solution. But maybe there is no such thing. Perhaps a heuristic in html export to just take care of the error: if it looks like a numbered list item but there is no item body, bail and assume it's part of the text. Or a combination of that together with the item number > 1. Would that work? Nick > Regards, > > -- > Nicolas >