From: Christian Moe <mail@christianmoe.com>
To: Skip Collins <skip.collins@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: outline formatting in html
Date: Fri, 06 May 2011 11:32:56 +0200 [thread overview]
Message-ID: <4DC3C048.7000209@christianmoe.com> (raw)
In-Reply-To: <BANLkTinLyLCMRAwMsB5n6Nd1chzMWx8=OA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
Hi,
That would be a good feature to have. While waiting for someone to
patch it in, a workaround for HTML output would be to turn off section
numbering and then fake it with CSS. I enclose a four-level example I
happen to have lying around. You can extend if needed (note that the
title becomes h1, so the top-level heading is h2).
Yours,
Christian
On 5/6/11 5:59 AM, Skip Collins wrote:
> I thought this would be easy. But I cannot find a way to get html
> formatted the way I want. I would like to view org content in
> "traditional" outline format, with indentation, Roman numerals for
> the top level heading, etc:
>
> I. This is a top level heading
> II. Here is another level-1 heading
> A. Here is a level 2 heading
> 1. This is a level-3 heading
> 2. Another level-3
> a. Level-4
> b. Another level-4
> (1) Level-5
> (a) Level-6
> B. Another level 2
>
> When I customize org-export-section-number-format, I do not get
> exactly what I want in html output. All heading numbers include
> higher level numbers, e.g. II.A.2.b. I am looking for a less cluttered
> output in which a heading only includes the single counter for its level.
>
>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: css-simple-outline.css --]
[-- Type: text/css; name="css-simple-outline.css", Size: 507 bytes --]
body {
counter-reset: head1 head2 head3 head4;
}
.outline-2 h2:before {
counter-increment: head1;
content: counter(head1, upper-roman) ". ";
}
h2 {
counter-reset: head2 head3 head4;
}
h3:before {
counter-increment: head2;
content: counter(head2, upper-latin) ". ";
}
h3 {
counter-reset: head3 head4;
}
h4:before {
counter-increment: head3;
content: counter(head3, decimal) ". ";
}
h4 {
counter-reset: head4;
}
h5:before {
counter-increment: head4;
content: counter(head4, lower-latin) ". ";
}
[-- Attachment #3: css-simple-outline.org --]
[-- Type: text/plain, Size: 370 bytes --]
#+TITLE: css-simple-outline.org
#+OPTIONS: H:4 num:nil toc:nil
#+STYLE: <link href="css-simple-outline.css" type="text/css" rel="stylesheet" />
* Top heading, Level 1 (I)
** Level 2 subhead (A)
*** Level 3 subhead (1)
**** Level 4 subhead (a)
**** Level 4 subhead (b)
*** Level 3 subhead (2)
**** Level 4 subhead (a)
***** Level 5 subhead (no formatting)
next prev parent reply other threads:[~2011-05-06 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 3:59 outline formatting in html Skip Collins
2011-05-06 9:32 ` Christian Moe [this message]
2011-05-06 14:27 ` Skip Collins
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=4DC3C048.7000209@christianmoe.com \
--to=mail@christianmoe.com \
--cc=emacs-orgmode@gnu.org \
--cc=skip.collins@gmail.com \
/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
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
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).