From: plutek-infinity <plutek@infinity.net>
To: emacs-orgmode@gnu.org
Subject: html export page title
Date: Tue, 20 Jan 2009 14:51:13 -0500 [thread overview]
Message-ID: <87wscpdadq.fsf@paldesk2.palstudio> (raw)
greetings!
i'm wondering what is the best way to designate the web-page title when doing html export from org-mode. i'm *not* talking about what is done by the #+TITLE: variable, because this puts a title in the page content AND gives a browser title. i'm looking for some way to set only the <head> title element in the exported html, *without* that title also showing up within the page content.
i don't see anything to do that currently, short of manually inserting a unique <title> element in the <head> section of the exported html.
thanks very much... cheers!
--
.pltk.
reply other threads:[~2009-01-20 19:50 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=87wscpdadq.fsf@paldesk2.palstudio \
--to=plutek@infinity.net \
--cc=emacs-orgmode@gnu.org \
/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).