emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: James Harkins <jamshark70@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Seeking advice on a worg contribution
Date: Tue, 06 May 2014 08:45:58 +0200	[thread overview]
Message-ID: <m2vbtjh0bd.fsf@internet-188-198-242-86.narocnik.mobitel.si> (raw)
In-Reply-To: <f4d6444a-92b3-4378-ab2a-8c8640c2c8ef@dewdrop-world.net>

James Harkins writes:

>> The HTML code produced by the normal HTML export, which is what I assume
>> Worg uses, has the captions as special label classes (org-src-name) so
>> CSS could easily be defined if not there already.
> Let's assume I'm an HTML idiot (which is true...). Is it really true, 
> according to [1], that the only way to add this CSS class definition is to 
> put it in a separate file and link it? It seems to be the only *documented* 
> method.
> [1] http://orgmode.org/manual/CSS-support.html#CSS-support


This is the bit of [1] that you were looking for: "You could also
directly write a <style> </style> section in this way, without referring
to an external file."

Like this:

#+HTML_HEAD: <style>org-src-name {color: blue; }</style>

(I haven't gone back over the discussion to see what you want to do with
captions, so coloring them blue is just an example.)

You can also use multiple HTML_HEAD lines, e.g.:

#+HTML_HEAD: <style>
#+HTML_HEAD:  p {text-indent: 1em; line-height: 150%}
#+HTML_HEAD:  p.footnote {font-size: x-small}
#+HTML_HEAD: </style>

...but if you have more than a few of those, you *will* want to put them
in a separate file and link them.


  reply	other threads:[~2014-05-06  6:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04  1:38 Seeking advice on a worg contribution James Harkins
2014-05-05 17:04 ` Eric S Fraga
2014-05-06  2:17   ` James Harkins
2014-05-06  6:45     ` Christian Moe [this message]
2014-05-06  7:30     ` Eric S Fraga
2014-05-06 10:08 ` Bastien
2014-05-06 11:46   ` James Harkins
2014-05-06 12:35     ` Bastien
2014-05-06 14:41   ` James Harkins
2014-05-07  9:08     ` Bastien

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:

  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=m2vbtjh0bd.fsf@internet-188-198-242-86.narocnik.mobitel.si \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jamshark70@gmail.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


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).