From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Rose Subject: Re: Preventing line breaks in (HTML) published description lists Date: Mon, 06 Jul 2009 12:46:58 +0200 Message-ID: <873a9accm5.fsf@kassiopeya.MSHEIMNETZ> References: <4A5075C7.6020509@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MNlf1-0002Ff-9A for emacs-orgmode@gnu.org; Mon, 06 Jul 2009 06:42:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MNlev-0002EW-G4 for emacs-orgmode@gnu.org; Mon, 06 Jul 2009 06:42:57 -0400 Received: from [199.232.76.173] (port=36784 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MNlev-0002ET-BP for emacs-orgmode@gnu.org; Mon, 06 Jul 2009 06:42:53 -0400 Received: from mail.gmx.net ([213.165.64.20]:35494) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1MNleu-0002zu-Ot for emacs-orgmode@gnu.org; Mon, 06 Jul 2009 06:42:53 -0400 In-Reply-To: <4A5075C7.6020509@gmail.com> (Paul Michael Reilly's message of "Sun, 05 Jul 2009 05:43:35 -0400") 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: Paul Michael Reilly Cc: emacs-orgmode@gnu.org Paul Michael Reilly writes: > I added a plain list to my file: > > ... > - term1 :: this means something > - term2 :: this means something else > - term3 :: and something different still > ... > > fully expecting the term and the description rendered in HTML to be on the same > line as is shown in the Latex published Org Mode manual. But the items were > rendered as: > > ... > term1 > this means something > term2 > this means something else > term3 > and something different still > ... > > I suspect this might be an HTML artifact, nevertheless, how would I convince > org-mode to arrange for the HTML rendering to attempt to keep the terms and > descriptions on the same line? An example or reference would be much > appreciated. Don't use a definition list at all: - *term1* this means something - *term2* this means something else - *term3* and something different still Sebastian