From: Eric S Fraga <email@example.com>
To: James Harkins <firstname.lastname@example.org>
Cc: orgmode <email@example.com>
Subject: Re: Seeking advice on a worg contribution
Date: Mon, 5 May 2014 18:04:38 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (James Harkins's message of "Sun, 4 May 2014 09:38:27 +0800")
On Sunday, 4 May 2014 at 09:38, James Harkins wrote:
> I finally finished a draft (attached, and not carefully proofread yet)
> of a new worg page to outline what I had to do for a big Beamer
> publishing project.
Interesting and very useful document. Thanks!
> Could somebody look it over and advise of any
> formatting problems? I guess it should be basically OK; I copied the
> standard worg header, and I stuck to normal org markup throughout.
The only thing I would suggest is changing H:2 to H:3 as your 3rd level
headings are being converted into bullet list items.
> A specific formatting question: I have several source code blocks with
> captions. The captions are formatted exactly the same as normal
> paragraphs. Will worg use a different CSS style for captions? If not,
> what do I have to do to make it do that? (At least, display the
> captions slightly smaller.)
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.
: Eric S Fraga (0xFFFCF67D), Emacs 184.108.40.206, Org release_8.2.6-923-g233c11
next prev parent reply other threads:[~2014-05-05 17:04 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 [this message]
2014-05-06 2:17 ` James Harkins
2014-05-06 6:45 ` Christian Moe
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
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 \
* 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).