From: Stefan Vollmar <firstname.lastname@example.org> To: emacs-orgmode <email@example.com> Subject: Structured export of HTML headlines Date: Fri, 03 Jul 2009 13:54:42 +0200 [thread overview] Message-ID: <5DE4EAC1-E841-4C7E-B022-8585D9253654@nf.mpg.de> (raw) Hello, org's HTML output is very convincing (as are so many other wonderful things org does) - congratulations! We now want to use it also for our software documentation. Our main packages are Qt 4.5 based and we have already had some good experiences with using Qt's help browser, http://doc.trolltech.com/4.5/assistant-details.html , and find it highly recommendable. Previous versions of our documentation were written in LaTeX, converted to HTML with tth and then post-processed with some (rather complicated) Python code we have written. To use QtAssistant, one has to create a XML file which looks like this: <DCF ref="vhist.htm#doc:begin" title="VHIST White Paper"> <section ref="vhist.htm#sec:abstract" title="Abstract"> </section> [...] <section ref="vhist.htm#tth_sEc4.10" title="Comments on specific Design Decisions"> <section ref="vhist.htm#tth_sEc4.10.1" title="The syntax of VHIST markers"> </section> <section ref="vhist.htm#tth_sEc4.10.2" title="Comments on Attribute filetype"> </section> </section> </DCF> To create such a dcf-file it would be helpful to have a list with all HTML headings (level 1-3) and their URLs. It is, of course, possible to extract them from the HTML file but I guess there are more elegant ways as org, obviously, knows about the structure of all HTML files in a publishing project. Many thanks in advance. Warm regards, Stefan -- Dr. Stefan Vollmar, Dipl.-Phys. Max-Planck-Institut für neurologische Forschung Gleuelerstr. 50, 50931 Köln, Germany Tel.: +49-221-4726-213 FAX +49-221-4726-298 Tel.: +49-221-478-5713 Mobile: 0160-93874279 Email: firstname.lastname@example.org http://www.nf.mpg.de
reply other threads:[~2009-07-03 11:54 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5DE4EAC1-E841-4C7E-B022-8585D9253654@nf.mpg.de \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Structured export of HTML headlines' \ /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).