From: Paul Michael Reilly <firstname.lastname@example.org> To: Sebastian Rose <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Preventing line breaks in (HTML) published description lists Date: Mon, 06 Jul 2009 08:38:08 -0400 [thread overview] Message-ID: <4A51F030.email@example.com> (raw) In-Reply-To: <873a9accm5.fsf@kassiopeya.MSHEIMNETZ> [-- Attachment #1.1: Type: text/plain, Size: 1475 bytes --] On 07/06/2009 06:46 AM, Sebastian Rose wrote: > Paul Michael Reilly<firstname.lastname@example.org> 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 > FWIW, this solution is better than using a CSS style based solution but it had the nit that the bullet (o) is present in the output (of course) where the description list had no bullet. After playing around with this a bit I decided that your point, don't use a description list, is well taken. I wound up using a simple table instead and got very satisfying results. Thanks, -pmr [-- Attachment #1.2: Type: text/html, Size: 1898 bytes --] [-- Attachment #2: Type: text/plain, Size: 204 bytes --] _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacsemail@example.com http://lists.gnu.org/mailman/listinfo/emacs-orgmode
prev parent reply other threads:[~2009-07-06 12:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-07-05 9:43 Paul Michael Reilly 2009-07-05 13:33 ` Bernt Hansen 2009-07-05 18:18 ` Paul Michael Reilly 2009-07-06 10:46 ` Sebastian Rose 2009-07-06 12:38 ` Paul Michael Reilly [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4A51F030.firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Preventing line breaks in (HTML) published description lists' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).