From: Sebastian Rose <sebastian_rose@gmx.de>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Bernt Hansen <bernt@norang.ca>, Eraldo Helal <eraldo@eraldo.org>,
Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: Re: html export - howto change UP|HOME link style?
Date: Tue, 17 Nov 2009 15:51:06 +0100 [thread overview]
Message-ID: <87d43hgq79.fsf@gmx.de> (raw)
In-Reply-To: <C242CD75-35DA-4B3C-9BD4-24E6A79B8740@gmail.com> (Carsten Dominik's message of "Tue, 17 Nov 2009 15:12:15 +0100")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> OK, I have applied the patch.
>
> But: Is it really correct that these links should be inside the content div?
Hm - this is a matter of taste. I thought I had changed it...
Good question.
Pros:
Some people might restrict the content div to a certain size or frame
and would like it this way.
Cons:
If people choose to extract the content div to put it's contents into
some framework, they probably wouldn't want those links there.
But they could simply ommit LINK_HOME/UP, so...
One could always put those links in the margin of the content div, or
even outside, using CSS.
Sebastian
>
> - Cartsen
>
> On Nov 15, 2009, at 12:02 AM, Sebastian Rose wrote:
>
>> Bernt Hansen <bernt@norang.ca> writes:
>>> ,----[ test.org exported to HTML buffer ]
>>> | <head>
>>> | <div style="text-align:right;font-size:70%;white-space:nowrap;">
>>> | <a accesskey="h" href="up_goes_here"> UP </a>
>>> | |
>>> | <a accesskey="H" href="home_goes_there"> HOME </a>
>>> | </div>
>>> |
>>> | <title>test.org</title>
>>> `----
>>>
>>> Shouldn't the up and home links both be moved to the body of the page,
>>> stripped of their in-line style info (text-align, font-size,
>>> white-space) and use CSS for this instead? I think that might be more
>>> flexible for formatting.
>>
>>
>>
>> This patch fixes it. I've put the LINK_UP and ..._HOME directly after
>> the <body> tag:
>>
>> <body>
>> ----- HERE ---
>> <div id="content">
>>
>> ..
>>
>>
>> The links can be formated customizing the variable
>>
>> `org-export-html-home/up-format'
>>
>>
>>
>> Sebastian
>>
>>
>> diff --git a/lisp/org-html.el b/lisp/org-html.el
>> index 11a692e..66cc86b 100644
>> --- a/lisp/org-html.el
>> +++ b/lisp/org-html.el
>> @@ -753,7 +753,6 @@ PUB-DIR is set, use this as the publishing directory."
>> <html xmlns=\"http://www.w3.org/1999/xhtml\"
>> lang=\"%s\" xml:lang=\"%s\">
>> <head>
>> -%s
>> <title>%s</title>
>> <meta http-equiv=\"Content-Type\" content=\"text/html;charset=%s\"/>
>> <meta name=\"generator\" content=\"Org-mode\"/>
>> @@ -765,6 +764,7 @@ lang=\"%s\" xml:lang=\"%s\">
>> </head>
>> <body>
>> <div id=\"content\">
>> +%s
>> "
>> (format
>> (or (and (stringp org-export-html-xml-declaration)
>> @@ -775,17 +775,17 @@ lang=\"%s\" xml:lang=\"%s\">
>> "")
>> (or charset "iso-8859-1"))
>> language language
>> + (org-html-expand title)
>> + (or charset "iso-8859-1")
>> + date author description keywords
>> + style
>> (if (or link-up link-home)
>> (concat
>> (format org-export-html-home/up-format
>> (or link-up link-home)
>> (or link-home link-up))
>> "\n")
>> - "")
>> - (org-html-expand title)
>> - (or charset "iso-8859-1")
>> - date author description keywords
>> - style))
>> + "")))
>>
>> (org-export-html-insert-plist-item opt-plist :preamble opt-
>> plist)
>>
>
> - Carsten
next prev parent reply other threads:[~2009-11-17 14:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 16:51 html export - howto change UP|HOME link style? Eraldo Helal
2009-11-14 22:22 ` Bernt Hansen
2009-11-14 22:52 ` Sebastian Rose
2009-11-14 23:02 ` Sebastian Rose
2009-11-15 5:13 ` Eraldo Helal
2009-11-15 5:52 ` Sebastian Rose
2009-11-17 1:31 ` Eraldo Helal
2009-11-17 3:17 ` Sebastian Rose
2009-11-17 14:12 ` Carsten Dominik
2009-11-17 14:51 ` Sebastian Rose [this message]
2009-11-18 5:43 ` Carsten Dominik
2009-11-18 13:11 ` Sebastian Rose
2009-11-21 8:37 ` Eraldo Helal
2009-11-21 11:52 ` Carsten Dominik
2009-11-21 14:34 ` Eraldo Helal
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=87d43hgq79.fsf@gmx.de \
--to=sebastian_rose@gmx.de \
--cc=bernt@norang.ca \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eraldo@eraldo.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).