From: Jonathan Leech-Pepin <firstname.lastname@example.org> To: Sebastian Wiesner <email@example.com> Cc: Org Mode Mailing List <firstname.lastname@example.org>, Mike McLean <email@example.com> Subject: Re: Online manual Date: Sun, 24 Feb 2013 12:53:41 -0500 [thread overview] Message-ID: <CAEWDx5cpRohh6R130nG5cz=rqQB_i-zwjfAPfzxh7ZoDyhSPPw@mail.gmail.com> (raw) In-Reply-To: <CALf2awTCVTGSW_GR__8=oLrgfPusP7RM4uyZ9QddO0fTtOfDbQ@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1027 bytes --] Hello, On Feb 24, 2013 11:48 AM, "Sebastian Wiesner" <firstname.lastname@example.org> wrote: > > 2013/2/24 Mike McLean <email@example.com>: > > > > On Feb 24, 2013, at 11:03 AM, Sebastian Wiesner <firstname.lastname@example.org> wrote: > > > >> Hello, > >> > >> how is the online manual of Org mode  rendered? Especially, how is > >> the awesome table of contents on the right sight created? > > > > It is done through CSS and I do something similar with most of my HTML exports. I have a custom CSS that I load by having the following in every Org file. > > So is the Org manual written in Org? I thought it was written in > Texinfo. After all, there is a Texinfo document in the Org sources > . Is this Texinfo document generated from some Org document? > Generally, can Org be exported to Texinfo/Info? > > : http://orgmode.org/cgit.cgi/org-mode.git/tree/doc/org.texi > Currently the manual is in info, however the new exporter has a texinfo exporter and I know that Thomas Dye is working on converting it to org. Regards, Jon [-- Attachment #2: Type: text/html, Size: 1521 bytes --]
next prev parent reply other threads:[~2013-02-24 17:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-24 16:03 Sebastian Wiesner 2013-02-24 16:37 ` Mike McLean 2013-02-24 16:48 ` Sebastian Wiesner 2013-02-24 17:52 ` Thomas S. Dye 2013-02-24 17:53 ` Jonathan Leech-Pepin [this message] -- strict thread matches above, loose matches on Subject: below -- 2009-06-29 13:24 Shaun Johnson 2009-06-30 5:03 ` Carsten Dominik 2009-06-30 5:05 ` Carsten Dominik 2009-06-30 8:30 ` Shaun Johnson
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='CAEWDx5cpRohh6R130nG5cz=rqQB_i-zwjfAPfzxh7ZoDyhSPPw@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Online manual' \ /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).